| 3 | Approval of the Agenda | |
|---|---|---|
| R3-243001 | RAN3#124 Meeting Agenda | RAN3 Chair |
| 4 | Approval of the minutes from previous meetings | |
| R3-243002 | RAN3#123-bis Meeting Report | ETSI-MCC |
| 5 | Documents for immediate consideration | |
| R3-243003 | Guidelines for RAN3 Meetings | RAN3 Chair, RAN3 Vice-Chairs |
| 7 | General, protocol principles and issues | |
| R3-243004 | TR 30.531 v1.52.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| 8.1 | New Incoming LSs | |
| R3-243005 | Reply LS on Restoration of N3mb Failure for MBS broadcast | CT4(Nokia) |
| R3-243011 | LS to RAN3 on MDT for NPN | RAN2(Ericsson) |
| R3-243012 | LS on emergency call support for (e)RedCap in barred cells | RAN2(Apple) |
| R3-243013 | LS on 5GS missing CBC support for shared networks | SA2(Ericsson) |
| R3-243015 | Reply LS on providing MBS assistance information from SMF towards NG-RAN node during Xn handover | SA2(Ericsson) |
| R3-243022 | LS on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | SA2(VIVO) |
| R3-243024 | LS to SA2 and RAN2 on selected satellite architecture for Store and Forward | SA3(Interdigital) |
| R3-243026 | Reply LS on area scope handling for QoE measurements | SA5(Ericsson) |
| R3-243027 | Reply LS on MDT measurements collection in MR-DC | SA5(Nokia) |
| R3-243028 | LS on MBS Communication Service Type | SA5(Ericsson) |
| R3-243113 | LS on inter-node RRC message for intra-SN SCPAC in MN format | RAN2(ZTE) |
| R3-243121 | Discussion on answers to RAN2 on MDT for NPN | Nokia |
| R3-243122 | [Draft] Reply LS on MDT for NPN | Nokia |
| R3-243123 | Correction of MDT for PNI-NPN | Nokia |
| R3-243137 | Discussion on emergency call support for (e)RedCap in barred cells | ZTE, China Telecommunication, China Unicom |
| R3-243138 | Introduction of barring exemption for RedCap UEs for emergency calls [RedCap_EM_Call] | ZTE, China Telecommunication, China Unicom |
| R3-243139 | Introduction of barring exemption for RedCap UEs for emergency calls [RedCap_EM_Call] | ZTE, China Telecommunication, China Unicom |
| R3-243140 | [Draft] Reply LS on emergency call support for (e)RedCap in barred cells | ZTE |
| R3-243154 | Introduction of barring exemption for RedCap UEs for emergency calls | China Telecom, ZTE,China Unicom |
| R3-243159 | Introduction of barring exemption for RedCap UEs for emergency calls | China Telecom, ZTE, China Unicom |
| R3-243209 | Discussion on LS on MDT measurements collection in MR-DC | Huawei |
| R3-243210 | Correction on MDT configuration in NR-DC | Huawei |
| R3-243211 | Discussion on LS to RAN3 on MDT for NPN | Huawei |
| R3-243212 | CR on MDT for NPN | Huawei |
| R3-243213 | CR on MDT for NPN | Huawei |
| R3-243214 | CR on MDT for NPN | Huawei |
| R3-243215 | [draft] Reply LS on MDT for NPN | Huawei |
| R3-243224 | Consideration on Restoration of N3mb Failure for MBS broadcast | Huawei, CBN |
| R3-243225 | Restoration of N3mb Failure for MBS broadcast | Huawei, CBN |
| R3-243226 | Restoration of N3mb Failure for MBS broadcast | Huawei, CBN |
| R3-243227 | [DRAFT] Reply LS on Restoration of N3mb Failure for MBS broadcast | Huawei |
| R3-243311 | Correction of MDT for PNI-NPN | Nokia |
| R3-243312 | Correction of MDT for PNI-NPN | Nokia |
| R3-243317 | Restoration of N3mb Failure | Nokia |
| R3-243318 | Correction of N3mb Path Failure | Nokia |
| R3-243319 | Response LS on Restoration of N3mb Failure for MBS Broadcast | Nokia |
| R3-243367 | MBS Communication Service Type for QMC | Ericsson |
| R3-243368 | [DRAFT] LS on MBS Communication Service Type | Ericsson |
| R3-243370 | Considerations on NTN Store and Forward Architectures | Ericsson LM |
| R3-243371 | [DRAFT] Reply LS on selected satellite architecture for Store and Forward | Ericsson LM |
| R3-243428 | Discussion on MDT NPN with draft LS | CATT, Samsung |
| R3-243473 | Considerations on RAN2 LS on emergency call support for (e)RedCap in barred cells | Ericsson |
| R3-243474 | Introduction of barring exemption for RedCap UEs for emergency calls [RedCap_EM_Call] | Ericsson |
| R3-243475 | Introduction of barring exemption for RedCap UEs for emergency calls [RedCap_EM_Call] | Ericsson |
| R3-243476 | Introduction of barring exemption for RedCap UEs for emergency calls [RedCap_EM_Call] | Ericsson |
| R3-243477 | Introduction of barring exemption for eRedCap UEs for emergency calls [eRedCap_EM_Call] | Ericsson |
| R3-243478 | Introduction of barring exemption for eRedCap UEs for emergency calls [eRedCap_EM_Call] | Ericsson |
| R3-243479 | Introduction of barring exemption for eRedCap UEs for emergency calls [eRedCap_EM_Call] | Ericsson |
| R3-243480 | [DRAFT]Response LS on LS on emergency call support for (e)RedCap in barred cells | Ericsson |
| R3-243510 | Discussion on MDT for NPN | Ericsson |
| R3-243511 | Reply LS on MDT for NPN | Ericsson |
| R3-243512 | Corrections on MDT for PNI-NPN | Ericsson |
| R3-243513 | Corrections on MDT for PNI-NPN | Ericsson |
| R3-243514 | Corrections on MDT for PNI-NPN | Ericsson |
| R3-243517 | Signalling based immediate MDT in NR-DC | Ericsson |
| R3-243518 | Reply LS on MDT configuration control in NR-DC | Ericsson |
| R3-243519 | Indicator to control the node collecting MDT measurements in the case of DC configurations | Ericsson |
| R3-243520 | Indicator to control the node collecting MDT measurements in the case of DC configurations | Ericsson |
| R3-243521 | Indicator to control MDT measurements in the case of NR-DC configurations | Ericsson |
| R3-243532 | Indicator to control the node collecting MDT measurements in the case of DC configurations | Ericsson |
| R3-243540 | On the Reply LS from CT4 about N3mb restoration in case of path failure for NR MBS | Ericsson |
| R3-243541 | Introduction of support of NG-U restoration of broadcast MBS sessions | Ericsson |
| R3-243542 | Introduction of support of NG-U restoration of broadcast MBS sessions | Ericsson |
| R3-243543 | [DRAFT] Reply LS on Restoration of N3mb Failure for MBS broadcast | Ericsson |
| R3-243577 | Discussion on N3mb User Plane Failure | CATT |
| R3-243591 | Corrections to support intra-SN S-CPAC in MN format Option 1 | ZTE |
| R3-243592 | Corrections to support intra-SN S-CPAC in MN format Option 2 | ZTE |
| R3-243593 | [DRAFT] Reply LS on intra-SN SCPAC in MN format | ZTE |
| R3-243621 | Emergency call support for (e)RedCap in barred cells | Huawei |
| R3-243622 | Emergency call support for RedCap in barred cells [RedCap_EM_Call] | Huawei |
| R3-243623 | Emergency call support for RedCap in barred cells [RedCap_EM_Call] | Huawei |
| R3-243624 | Emergency call support for eRedCap in barred cells [RedCap_EM_Call] | Huawei |
| R3-243625 | Emergency call support for eRedCap in barred cells [RedCap_EM_Call] | Huawei |
| R3-243626 | [draft] reply LS on emergency call support for (e)RedCap in barred cells | Huawei |
| R3-243699 | Correction on MDT area scope | ZTE |
| R3-243700 | Correction on MDT area scope | ZTE |
| R3-243701 | Correction on MDT area scope | ZTE |
| R3-243702 | draft reply LS to RAN2 on MDT for NPN | ZTE |
| R3-243704 | Discussion on MDT for EN-DC | ZTE |
| R3-243705 | Correction on MDT configuration in MR-DC | ZTE |
| R3-243706 | Correction on MDT for EN-DC for XnAP | ZTE |
| R3-243707 | Correction on MDT for EN-DC for Stage2 | ZTE |
| R3-243746 | Discussion on inter-node design for S-CPAC | Ericsson |
| R3-243747 | [DRAFT] Reply LS on inter-node RRC message for intra-SN SCPAC in MN format | Ericsson |
| R3-243763 | Support of Emergency Calls for (e)RedCap UEs in barred cells | Nokia |
| R3-243764 | Support of Emergency Calls for (e)RedCap UEs in barred cells | Nokia |
| R3-243765 | Support of Emergency Calls for (e)RedCap UEs in barred cells | Nokia |
| R3-243766 | Reply LS on Support of Emergency Calls for (e)RedCap UEs in barred cells | Nokia |
| R3-243771 | Response to R3-243540 and R3-243577 on N3mb failure detection | ZTE Corporation |
| R3-243775 | Reply LS on intra-SN SCPAC in MN format | RAN3(ZTE) |
| R3-243776 | CB:#5_MBSQoE | Ericsson |
| R3-243786 | Correction of N3mb Path Failure | Nokia |
| R3-243787 | Response LS on Restoration of N3mb Failure for MBS Broadcast | RAN3(Nokia) |
| R3-243804 | Correction on MDT configuration in NR-DC | Huawei |
| R3-243823 | CR on MDT for NPN | Huawei |
| R3-243829 | Restoration of N3mb Failure for MBS broadcast | Huawei, CBN, Nokia, Ericsson, CATT |
| R3-243838 | Correction on MDT for PNI-NPN | ZTE, Ericsson, Huawei, CATT |
| R3-243839 | Indicator on MDT configuration in MR-DC | ZTE, Ericsson, Huawei |
| R3-243873 | Corrections on MDT for PNI-NPN | CATT, Ericsson, ZTE, Huawei |
| R3-243882 | Indicator on MDT configuration in MR-DC | ZTE |
| R3-243885 | Reply LS on MDT for NPN | Ericsson |
| R3-243886 | Reply LS on MDT configuration control in NR-DC | Ericsson |
| R3-243887 | Correction of N3mb Path Failure | Nokia, Huawei, Ericsson, CATT |
| R3-243888 | Response LS on Restoration of N3mb Failure for MBS Broadcast | RAN3(Nokia) |
| R3-243889 | Correction on MDT for PNI-NPN | ZTE, Ericsson, Huawei, CATT |
| R3-243890 | Corrections on MDT for PNI-NPN | CATT, Ericsson, ZTE, Huawei, Nokia |
| R3-243891 | Corrections on MDT for PNI-NPN | Huawei, Ericsson, ZTE, Nokia |
| R3-243892 | Reply LS on MDT for NPN | RAN3(Ericsson) |
| R3-243935 | Correction on MDT configuration in MR-DC | Huawei, Ericsson, ZTE |
| R3-243936 | Indicator on MDT configuration in MR-DC | ZTE |
| R3-243937 | Reply LS on MDT configuration control in NR-DC | RAN3(Ericsson) |
| 8.2 | LSin received during the meeting | |
| R3-243788 | Reply LS on SRS bandwidth aggregation | RAN1(ZTE) |
| 8.3 | Left over LSs / pending actions | |
| R3-243030 | Reply LS on the user consent for trace reporting | SA5(Ericsson) |
| R3-243320 | Switch to RRC Connected after SDT Partial Context Transfer | Nokia, Ericsson |
| R3-243321 | Correction of switch to RRC connected after SDT Partial Context Transfer | Nokia, Ericsson |
| R3-243322 | Correction of switch to RRC connected after SDT Partial Context Transfer | Nokia, Ericsson |
| R3-243323 | Response LS on SDT signalling optimization for partial context transfer | Nokia, Ericsson |
| R3-243488 | Discussion on Improved KPIs | Nokia |
| R3-243489 | [Draft] Reply LS to SA5 on improved KPIs involving end-to-end data volume transfer time analytics | Nokia |
| R3-243504 | Further discussion related to the Reply LS on improved KPIs | Ericsson, CATT |
| R3-243505 | Reply LS on improved KPIs | Ericsson, CATT |
| R3-243506 | Discussions on User Consent corrections | Ericsson, Deutsche Telekom, AT&T |
| R3-243507 | Correction on user consent for trace reporting | Ericsson, Deutsche Telekom, AT&T |
| R3-243508 | Correction on user consent for trace reporting | Ericsson, Deutsche Telekom, AT&T |
| R3-243509 | Reply LS on user consent corrections | Ericsson, Deutsche Telekom, AT&T |
| R3-243703 | Correction on User consent for trace reporting | ZTE |
| R3-243730 | Correction of TS 38.401 on user consent | CMCC, Ericsson |
| R3-243731 | Discussion on user consent corrections | CMCC |
| R3-243768 | UE selection for user consent | Nokia |
| R3-243770 | Response to R3-243506, R3-243507, R3-243508, R3-243730 | Huawei Telecommunication India |
| R3-243777 | [Draft] Reply LS to SA5 on improved KPIs involving end-to-end data volume transfer time analytics | Nokia |
| R3-243778 | CB:#7_ImprovedKPIs | Nokia |
| R3-243880 | Correction on user consent | CMCC, Ericsson, ZTE |
| R3-243881 | Correction on user consent for trace reporting | Ericsson, AT&T, Deutsche Telekom, ZTE, CMCC |
| R3-243924 | Correction on user consent for trace reporting | Ericsson, AT&T, Deutsche Telekom, ZTE, CMCC |
| R3-243929 | Correction on user consent | CMCC, Ericsson, ZTE, Nokia, Huawei |
| R3-243938 | Correction on user consent for trace reporting | Ericsson, AT&T, Deutsche Telekom, ZTE, CMCC, Nokia, Huawei |
| R3-243941 | Reply LS to SA5 on improved KPIs involving end-to-end data volume transfer time analytics | RAN3(Nokia) |
| 9.1 | LTE | |
| R3-243009 | Reply LS on UE Location Information for NB-IoT NTN | RAN2(Qualcomm) |
| R3-243348 | Support User Location Information reporting for NB-IoT NTN | Nokia, Nokia Shanghai Bell, Qualcomm |
| R3-243372 | [DRAFT] Reply LS on UE Location Information for NB-IoT NTN | Ericsson, Huawei, Apple, Thales |
| R3-243373 | E-SMLC OAM Configuration for IoT NTN | Ericsson, Thales, Huawei |
| R3-243427 | Discussion on UE Location Information for NB-IoT NTN with draft LS | CATT |
| R3-243429 | Support of 2Rx XR UE inter system S1/NG-handover [2Rx_XR_Device] | Ericsson LM |
| R3-243431 | Discussion on UE Location Information for NB-IoT NTN | Huawei, Ericsson, Apple |
| R3-243443 | Considerations on RedCap/eRedCap UE inter-RAT inter-system S1/NG-handover | Ericsson, Qualcomm Inc., China Telecom, Vodafone |
| R3-243444 | Correction on RedCap UE inter-system S1/NG-handover | Ericsson, Qualcomm Inc., China Telecom, Vodafone |
| R3-243445 | Correction on RedCap UE inter-system S1/NG-handover | Ericsson, Qualcomm Inc., China Telecom, Vodafone |
| R3-243446 | Correction on eRedCap UE inter-system S1/NG-handover | Ericsson, Qualcomm Inc., China Telecom, Vodafone |
| R3-243554 | (TP for TS36.300) Discussion on UE Location for NTN NB-IoT UE | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-243555 | Draft Reply for LS on UE Location Information for NB-IoT NTN | Qualcomm Incorporated |
| R3-243566 | Discussion on UE Location Information for NB-IoT NTN | Huawei, Ericsson, Apple |
| R3-243576 | Correction on UE location information reporting for NB-IoT NTN | ZTE |
| R3-243631 | Support of UE location information for NB-IoT NTN | China Telecommunication |
| R3-243633 | Discussion on handover restriction of (e)RedCap | CATT, China Telecom, Vodafone |
| R3-243634 | Correction to 36.413 for Handover Restriction List (R17) | CATT, China Telecom, Vodafone |
| R3-243635 | Correction to 36.413 for Handover Restriction List (R18) | CATT, China Telecom, Vodafone |
| 9.2 | NR | |
| R3-243006 | LS on Restoration procedures for Split PDU Sessions | CT4(Ericsson) |
| R3-243007 | Reply LS on SRS BW aggregation impact on other channels/signals | RAN1(Huawei) |
| R3-243008 | Reply LS on questions on RAN1 parameter list | RAN1(CATT) |
| R3-243010 | LS to RAN1 on bandwidth aggregation | RAN2(ZTE) |
| R3-243014 | Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | SA2(Huawei) |
| R3-243016 | LS OUT on RAN feedback during handover | SA2(Huawei) |
| R3-243029 | LS reply on OAM requirements for UE location verification | SA5(CATT) |
| R3-243109 | Correction on stage 2 of PSCell List of RA report | ZTE, CATT, China Telecom |
| R3-243110 | Correction on PSCell List Container List of RA report | ZTE, CATT, China Telecom |
| R3-243111 | Correction on PSCell List Container List of RA report - XNAP | ZTE, CATT, China Telecom |
| R3-243112 | Correction on Inter-system MRO | Nokia, ZTE, Samsung, CMCC |
| R3-243116 | Resolution of MBS F1 User Plane Failure scenarios | Nokia, Huawei, Qualcomm Incorporated |
| R3-243117 | Correction of MBS F1-U failure Recovery - option 1 | Nokia, Huawei, Qualcomm Incorporated |
| R3-243118 | Correction of MBS F1-U failure Recovery - option 3 | Nokia, Huawei, Qualcomm Incorporated |
| R3-243119 | Correction of MBS F1-U failure Recovery - option 3 | Nokia, Huawei, Qualcomm Incorporated |
| R3-243120 | Correction of MBS NG-U Setup and non-shared gNB-DU | Nokia, Huawei, CATT, Qualcomm Incorporated |
| R3-243127 | Correction of Slice Availability and Support | Nokia, Deutsche Telekom, Ericsson, Huawei, CATT, ZTE |
| R3-243132 | Correction on indirect Data forwarding | ZTE, LG Electronics, China Telecommunication, Huawei, Samsung |
| R3-243141 | ASN.1 correction of CAG List for MDT | Nokia, Samsung, Huawei, ZTE, CATT, Ericsson |
| R3-243142 | ASN.1 correction of CAG List for MDT | Nokia, Samsung, Huawei, ZTE, CATT, Ericsson |
| R3-243143 | Addition of a missing indication in SN-initiated S-CPAC | Nokia |
| R3-243147 | Correction on the missing SIB18 in TS 38.473 | China Telecom, ZTE,CATT |
| R3-243148 | Correction on the missing SIB18 in TS 38.473 | China Telecom, ZTE, CATT |
| R3-243149 | Support of Emergency Services Support Indicator over NG and Xn interface | China Telecom |
| R3-243150 | Support of Emergency Services Support Indicator over NG interface | China Telecom, ZTE, China Unicom |
| R3-243151 | Support of Emergency Services Support Indicator over NG interface | China Telecom, ZTE,China Unicom |
| R3-243152 | Support of Emergency Services Support Indicator over NG interface | China Telecom, ZTE,China Unicom |
| R3-243153 | Support of Emergency Services Support Indicator over NG interface | China Telecom, ZTE, China Unicom |
| R3-243155 | Support of Emergency Services Support Indicator over Xn interface-R15 | ZTE, China Telecommunication, China Unicom |
| R3-243156 | Support of Emergency Services Support Indicator over Xn interface-R16 | ZTE, China Telecommunication, China Unicom |
| R3-243157 | Support of Emergency Services Support Indicator over Xn interface-R17 | ZTE, China Telecommunication, China Unicom |
| R3-243158 | Support of Emergency Services Support Indicator over Xn interface-R18 | ZTE, China Telecommunication, China Unicom |
| R3-243161 | Discussion on CFRA resource configurations in LTM | Google Inc. |
| R3-243162 | Corrections for CFRA resource provision in LTM | Google, Inc |
| R3-243179 | Correction of IP-Sec Transport Layer Address | Huawei, China Telecom, China Unicom, Ericsson, Nokia |
| R3-243180 | Correction of IP-Sec Transport Layer Address | Huawei, China Telecom, China Unicom, Ericsson, Nokia |
| R3-243181 | Correction of IP-Sec Transport Layer Address | Huawei, China Telecom, China Unicom, Ericsson, Nokia |
| R3-243182 | Correction of QoS Flow List | Huawei, Deutsche Telekom, CATT |
| R3-243183 | Correction of QoS Flow List | Huawei, Deutsche Telekom, CATT |
| R3-243184 | Correction of QoS Flow List | Huawei, Deutsche Telekom, CATT |
| R3-243185 | Effective measurement window for inter-RAT measurement | Huawei, China Telecom, China Unicom, Nokia |
| R3-243186 | Correction on Handover Cancel in CHO with SN for MR-DC | ZTE, Samsung, China Telecom, Ericsson |
| R3-243188 | SN-initiated flag signalling for SPR | Ericsson |
| R3-243216 | Discussion on CHO cancel in intra-DU | Huawei, LG Electronics Inc., Nokia, Ericsson |
| R3-243222 | [draft] Reply LS on RAN feedback during handover | Huawei |
| R3-243223 | Correction of handling GTP-U Error Indication | Ericsson, Nokia, Huawei |
| R3-243228 | Correction on BC session path update for network sharing | Huawei, CBN, Nokia, Qualcomm Incorporated, Samsung, CATT, ZTE |
| R3-243229 | Correction on MBS UP failure_option 1 | Huawei, CBN, Nokia, Qualcomm Incorporated |
| R3-243230 | Correction on partial succeed of Broadcast session [RedcapMBS] | Huawei, CMCC, CBN |
| R3-243231 | Correction on indirect data forwarding [Indirect Data forwarding] | Huawei, Nokia, Samsung, LG Electronics, ZTE |
| R3-243237 | Correction for 38.413 Reference specification | NEC, CMCC, NTT DOCOMO |
| R3-243238 | Correction for 38.413 Reference specification | NEC, CMCC, NTT DOCOMO |
| R3-243259 | Stage 2 correction for NR-U | Ericsson, Huawei, Qualcomm Incorporated, Nokia |
| R3-243276 | Correction on definition of AI/ML terminology | Samsung, ZTE, China Telecom, China Unicom |
| R3-243277 | Correction of source UE AP IDs in SN addition procedure | Samsung, Nokia, Ericsson, ZTE |
| R3-243280 | Addition of SON for fast MCG recovery in stage 2 | Samsung, Lenovo, CATT, Nokia, ZTE |
| R3-243281 | Issue on inter-system MRO | Samsung, ZTE, Nokia, CMCC |
| R3-243282 | Correction on Inter-system MRO | Samsung, ZTE, Nokia, CMCC |
| R3-243283 | Correction on Inter-system MRO | Samsung, Nokia, ZTE, CMCC |
| R3-243284 | Addition of CPAC detection in stage 2 | Samsung, Lenovo, CATT, Cybercore |
| R3-243286 | SPR forwarding | Samsung, Lenovo, Cybercore |
| R3-243287 | Correcting IE referenced in Coverage Modification | Huawei |
| R3-243288 | Correcting IE referenced in Coverage Modification | Huawei |
| R3-243301 | Support of PDCP SN Gap Report | Xiaomi |
| R3-243302 | Discussion on Efficient PDU Discard in CU-DU Split Architecture | Xiaomi |
| R3-243303 | Support of discard coordination between CU and DU | Xiaomi |
| R3-243304 | Support of discard coordination between CU and DU | Xiaomi |
| R3-243307 | Support of the pre-Configured SRS activation | Xiaomi, Ericsson, Nokia, Qualcomm Incorporated |
| R3-243308 | IAB-node authorization | CATT, Ericsson, ZTE |
| R3-243309 | IAB-node authorization | CATT, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-243310 | Correction of Recovery of Split PDU Session | ZTE, Nokia, Huawei,Deutsche Telekom, Ericsson |
| R3-243313 | QoE/RVQoE measurement continuity for SCG/MCG failure scenarios | Nokia |
| R3-243314 | Introduction of cell DTX/DRX information | Nokia |
| R3-243324 | Issue with AoI for Slice subject to Area Restriction | Nokia |
| R3-243325 | Corrections on preamble index allocation for intra-CU LTM | Ericsson, ZTE, Lenovo, Verizon, T-Mobile USA |
| R3-243326 | QoE measurement handling in RRC_IDLE and RRC_INACTIVE states | CATT, Ericsson, ZTE, Xiaomi |
| R3-243335 | Correction on the UL and DL congestion information | Huawei, CMCC, Deutsche Telekom, Nokia, Nokia Shanghai Bell, CATT |
| R3-243336 | Discussion on DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Qualcomm |
| R3-243337 | Correction on DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Xiaomi, Qualcomm |
| R3-243338 | Correction on DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Qualcomm |
| R3-243347 | Missing procedure description for pre-configured SRS activation | Qualcomm Incorporated, Ericsson, Nokia, Xiaomi |
| R3-243359 | Correction to DL-PRS Aggregation | Qualcomm Incorporated |
| R3-243360 | Correction to DL-PRS Aggregation | Qualcomm Incorporated |
| R3-243364 | Correction on AI/ML Terminology | Nokia, Huawei, Ericsson, Deutsche Telekom, InterDigital, NEC, Telecom Italia, CATT, Lenovo |
| R3-243365 | Restoration procedures for Split PDU Sessions | Huawei, Nokia, Deutsche Telekom, ZTE |
| R3-243366 | Correction of Recovery of Split PDU Session | Huawei, Nokia, Deutsche Telekom, ZTE, Ericsson |
| R3-243375 | Correction on LTM | Lenovo |
| R3-243376 | Correction on LTM | Lenovo |
| R3-243377 | Correction on End PDU Indication in Data Forwarding | Lenovo |
| R3-243378 | Correction on inter MN handover without SN change for QMC | Lenovo, Huawei |
| R3-243423 | Correction on stage 2 LTM | CATT, China Telecom, ZTE, CMCC |
| R3-243424 | Correction on the Assigned Criticality of LTM Cells To Be Released List IE | CATT, ZTE, Huawei, CMCC |
| R3-243430 | Support of pre-Configured SRS activation using full context relocation | Ericsson, Xiaomi, Nokia, Qualcomm Incorporated |
| R3-243434 | UE Context Release Command ASN.1 correction | Huawei, Nokia, CATT, ZTE, Samsung |
| R3-243435 | UE Context Release Command ASN.1 correction | Huawei, Nokia, CATT, ZTE, Samsung |
| R3-243436 | Correction on Measurement Reporting for BWA | Huawei, ZTE, Xiaomi |
| R3-243437 | Correction on Measurement Reporting for BWA | Huawei, ZTE, Xiaomi |
| R3-243438 | Correction on Measurement Time Window | Huawei |
| R3-243439 | Correction on Measurement Time Window | Huawei |
| R3-243440 | Logical TRP IDs management | Huawei |
| R3-243441 | Support of pre-configured SRS activation- Set1 | Huawei, CATT,Samsung, ZTE |
| R3-243442 | Support of pre-configured SRS activation- Set2 | Huawei, CATT,Samsung, ZTE |
| R3-243454 | Completion of LTM in Rel-18 | Ericsson |
| R3-243465 | Stage 2 corrections for AI/ML for NG-RAN | Huawei, Nokia, Ericsson, InterDigital, NEC, Deutsche Telekom, Telecom Italia, CATT, Lenovo |
| R3-243481 | Correction on UL-RSCP | Ericsson, Nokia, Qualcomm Inc. |
| R3-243482 | Correction on UL-RSCP | Ericsson, Nokia, Qualcomm Inc. |
| R3-243515 | Considerations on the Effective Measurement Window | Ericsson |
| R3-243516 | (draft) LS on terminology definitions for AI-ML in NG-RAN | Ericsson, Huawei, Nokia, Telecom Italia, InterDigital, Deutsche Telekom, Lenovo, NEC |
| R3-243524 | Correction on Rel-18 indirect data forwarding indication [Indirect Data Forwarding] | LG Electronics Inc. |
| R3-243525 | Final discussion on Rel-18 LTM UE based TA from CU to DU | LG Electronics Inc. |
| R3-243526 | Rel-18 LTM correction for UE-based TA information from CU to DU | LG Electronics Inc., Huawei, Lenovo, Samsung |
| R3-243527 | Rel-18 LTM correction for UE-based TA information from CU to DU | LG Electronics Inc., Huawei, Ericsson, Lenovo, Samsung, ZTE, CATT, Google, Nokia |
| R3-243533 | UP Restoration for a PDU Session with Dual Connectivity | Ericsson |
| R3-243534 | [Draft] Reply LS on Restoration procedures for a PDU Session with Dual Connectivity | Ericsson |
| R3-243538 | OAM requirements additions regarding AI/ML | Ericsson, Telecom Italia, Deutsche Telekom |
| R3-243539 | Correction of Recovery of split PDU Session | Nokia, Huawei, Deutsche Telekom, ZTE, CATT |
| R3-243568 | Support of pre-configured SRS activation- Set1 | Huawei, CATT,Samsung, ZTE |
| R3-243569 | Support of pre-configured SRS activation- Set2 | Huawei, CATT,Samsung, ZTE |
| R3-243570 | Update of stage 2 positioning information | Nokia, Ericsson, Huawei |
| R3-243578 | Discussion on definition of UE performance metrics | CATT, Deutsche Telekom, Nokia, China Telecom, China Unicom |
| R3-243579 | Stage 2 update on AI/ML for NG-RAN | CATT,Nokia,ZTE,Ericsson,Huawei |
| R3-243580 | Discussion on user plane failure handling | CATT |
| R3-243582 | Corrections on SL relay procedure | LG Electronics |
| R3-243589 | CR to 38.401 on general F1AP principles for multicast reception in RRC_INACTIVE | ZTE, Ericsson, CMCC |
| R3-243590 | CR to 38.401 on procedures of enabling multicast reception in RRC_INACTIVE | ZTE, Nokia, CBN, Huawei, Samsung, Lenovo, CATT, Qualcomm Incorporated |
| R3-243594 | Corrections on CG-CandidateList to support S-CPAC | ZTE, Ericsson, CATT, China Telecom, CMCC, Samsung |
| R3-243600 | Correction on user plane failure handling (XnAP) | CATT |
| R3-243601 | Correction on user plane failure handling (F1AP) | CATT |
| R3-243602 | Correction on user plane failure handling (E1AP) | CATT |
| R3-243605 | (CR to 38.413) Correct the description of the selected PLMN indication in INITIAL UE MESSAGE | China Telecom, Huawei, CATT, ZTE, Ericsson |
| R3-243606 | (CR to 38.413) Correct the description of the selected PLMN indication in INITIAL UE MESSAGE | China Telecom, Huawei, CATT, ZTE, Ericsson |
| R3-243610 | Correction on Handover Cancel in CHO with SN for EN-DC | Samsung, ZTE, Ericsson |
| R3-243611 | Correction on Handover Cancel in CHO with SN for EN-DC | Samsung, ZTE, Ericsson |
| R3-243612 | Correction on configuration modification and release in CHO with candidate PSCells | Samsung, Huawei, CATT, ZTE, LG Electronics |
| R3-243613 | Correction to QMC support in NR-DC for RRC segmentation | Samsung, ZTE, Lenovo, China Unicom, CATT |
| R3-243614 | Correction to QMC support in NR-DC for session status | Samsung, Ericsson, Xiaomi, China Unicom, Qualcomm Incorporated |
| R3-243615 | Support of pre-configured SRS activation - Set2 | Samsung, CATT, Huawei, ZTE |
| R3-243616 | [draft] LS on area specific SRS configuration | Samsung, Huawei, CATT, ZTE |
| R3-243632 | Correction to 38.423 for SON features enhancement | CATT, Samsung, ZTE |
| R3-243655 | Correction on the missing SIB20 in TS 38.470 | ZTE, China Telecom, China Unicom |
| R3-243656 | Correction on the missing SIB20 in TS 38.470 | ZTE, China Telecom, China Unicom |
| R3-243657 | Correction on the missing SIB9 in TS 38.470 | ZTE, China Telecom, China Unicom |
| R3-243658 | Correction on the missing SIB9 in TS 38.470 | ZTE, China Telecom, China Unicom |
| R3-243659 | Correction on the missing SIB9 in TS 38.470 | ZTE, China Telecom, China Unicom |
| R3-243660 | Correction on NGAP to support the QoE mobility during NG-based inter-MN HO | ZTE, China Unicom, China Telecom, CMCC, Samsung, CATT |
| R3-243666 | Discussion on direct data forwarding in SCPAC | Samsung, CATT, Huawei, ZTE, Cybercore |
| R3-243667 | (CR to 38.423) Correction on direct data forwarding in SCPAC | Samsung, CATT, Huawei, Cybercore |
| R3-243678 | Further Consideration on pre-configured SRS activation | CATT, Huawei, ZTE, Samsung |
| R3-243679 | Support of pre-configured SRS activation - Set1 | CATT, Huawei, ZTE, Samsung |
| R3-243680 | Support of pre-configured SRS activation - Set2 | CATT, Huawei, ZTE, Samsung |
| R3-243681 | Further consideration on OAM requirements for UE location verification | CATT, Huawei, ZTE, Samsung, Nokia |
| R3-243682 | Correction to OAM requirement for UE location verification | CATT, Huawei, ZTE, Samsung, Nokia |
| R3-243683 | Corrections for LTM CSI Report Config generation | Google, Inc |
| R3-243684 | Support of Preconfigured SRS Activation - Set 1 | ZTE, CATT, Huawei, Samsung |
| R3-243685 | Support of Preconfigured SRS Activation - Set 2 | ZTE, CATT, Huawei, Samsung |
| R3-243687 | Discussion on LTM remaining issues | ZTE |
| R3-243689 | Discussion on Remaining issues for LTM | Samsung |
| R3-243695 | Discussion on Uu Relay RLC channel setup during UE context setup procedure | ZTE, China Telecom |
| R3-243696 | Corrections on SL relay | ZTE, China Telecom, Samsung |
| R3-243697 | Corrections on SL relay | ZTE, China Telecom, Samsung |
| R3-243698 | Corrections on Uu Relay RLC channel setup | ZTE, China Telecom |
| R3-243710 | Correction on the QMC information in the SN modification required message | Huawei, China Unicom, Ericsson, Lenovo |
| R3-243711 | Further miscellaneous corrections to 38.300 | Huawei, China Unicom, Lenovo |
| R3-243712 | Further miscellaneous corrections to 37.340 | Huawei, China Unicom, Lenovo |
| R3-243720 | Correction on Data Collection procedures over Xn | CMCC, ZTE, CATT, Huawei, Lenovo, NEC |
| R3-243732 | Correction on inter-system MRO | CMCC, Samsung, ZTE, Nokia |
| R3-243741 | Correction on definition of AI/ML terminology | ZTE, Samsung, China Telecom, China Unicom |
| R3-243742 | Correction to 38.401 on IAB-node authorization | ZTE, CATT, Lenovo |
| R3-243743 | Correction to 38.401 on IAB-node authorization | ZTE, CATT, Lenovo |
| R3-243744 | Correction to 38.401 on mobile IAB-node authorization | ZTE, CATT, Lenovo |
| R3-243748 | Correction on Inter-system MRO | ZTE, Samsung, CMCC, Nokia |
| R3-243749 | Correction on Inter-system MRO | ZTE, Samsung, CMCC, Nokia |
| R3-243750 | Discussion on providing the PDCP version from the eNB-CP to the eNB-UP over the E1 interface | Samsung |
| R3-243751 | Correction on SIB23 in TS38.470 | ZTE, Ericsson, Huawei, CATT, Xiaomi, Nokia |
| R3-243752 | Correction on SIB23 in TS38.473 | ZTE, Ericsson, Huawei, CATT, Xiaomi, Nokia |
| R3-243757 | PDCP version information over the E1 interface | Samsung |
| R3-243758 | Correction on textual description of Early Status Transfer procedure | ZTE, CMCC, China Unicom, CATT, Samsung, Nokia |
| R3-243759 | Correction on textual description of Early Status Transfer procedure | ZTE, CMCC, China Unicom, CATT, Samsung, Nokia |
| R3-243760 | Correction on textual description of Early Status Transfer procedure | ZTE, CMCC, China Unicom, CATT, Samsung, Nokia |
| R3-243762 | Draft Reply for LS on RAN feedback during handover | Qualcomm Incorporated |
| R3-243773 | Issue with AoI for Slice subject to Area Restriction | Nokia, Deutsche Telekom |
| R3-243779 | Correction on Measurement Reporting for BWA | Huawei, ZTE, Xiaomi, Ericsson |
| R3-243780 | Correction on Measurement Reporting for BWA | Huawei, ZTE, Xiaomi, Ericsson |
| R3-243781 | CB:#9_GTP-Uerror | Huawei |
| R3-243782 | ASN.1 correction of CAG List for MDT | Nokia, Samsung, Huawei, ZTE, CATT, Ericsson, CMCC |
| R3-243783 | ASN.1 correction of CAG List for MDT | Nokia, Samsung, Huawei, ZTE, CATT, Ericsson, CMCC |
| R3-243784 | Stage 2 correction for NR-U | Ericsson, Huawei, Qualcomm Incorporated, Nokia |
| R3-243785 | Addition of SON for fast MCG recovery in stage 2 | Samsung, Lenovo, CATT, Nokia, ZTE |
| R3-243790 | LTM correction for UE-based TA information from CU to DU | LG Electronics Inc., Huawei, Ericsson, Lenovo, Samsung, ZTE, CATT, Google, Nokia, NEC |
| R3-243791 | CB:#12_Mobilityenh | Ericsson |
| R3-243792 | Correction on the UL and DL congestion information | Huawei, CMCC, Deutsche Telekom, Nokia, Nokia Shanghai Bell, CATT, ZTE, Ericsson, Qualcomm |
| R3-243793 | Support of PDCP SN Gap Report | Xiaomi, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Ericsson, Lenovo, CATT |
| R3-243794 | UE Context Release Command ASN.1 correction | Huawei, Nokia, CATT, ZTE, Samsung, Ericsson |
| R3-243795 | UE Context Release Command ASN.1 correction | Huawei, Nokia, CATT, ZTE, Samsung, Ericsson |
| R3-243796 | CB:#13_Positioning | CATT |
| R3-243797 | Correction on definition of AI/ML terminology | Samsung, ZTE, China Telecom, China Unicom |
| R3-243798 | Stage 2 corrections for AI/ML for NG-RAN | Huawei, Nokia, Ericsson, InterDigital, NEC, Deutsche Telekom, Telecom Italia, CATT, Lenovo |
| R3-243805 | Correction on Measurement Reporting for BWA | Huawei, ZTE, Xiaomi, Ericsson, Nokia, CATT |
| R3-243806 | Correction on Measurement Reporting for BWA | Huawei, ZTE, Xiaomi, Ericsson, Nokia, CATT |
| R3-243813 | Correction of Recovery of Split PDU Session | ZTE, Nokia, Huawei,Deutsche Telekom, Ericsson |
| R3-243814 | Correction of Recovery of Split PDU Session | Huawei, Nokia, Deutsche Telekom, ZTE, Ericsson |
| R3-243815 | Correction of Recovery of split PDU Session | Nokia, Huawei, Deutsche Telekom, ZTE, CATT, Ericsson |
| R3-243816 | Reply LS on Restoration procedures for a PDU Session with Dual Connectivity | RAN3(Ericsson) |
| R3-243817 | Correction on LTM | Lenovo, Ericsson, Huawei, Nokia, Samsung, CATT, LG Electronics, Google, China Telecom, ZTE |
| R3-243818 | Correction for CHO cancel in UE CONTEXT MODIFICATION REQUEST | Huawei |
| R3-243819 | Correction of MBS NG-U Setup and non-shared gNB-DU | Nokia, Huawei, CATT, Qualcomm Incorporated |
| R3-243821 | Correction of MBS F1-U failure Recovery - option 1 | Nokia, Huawei, Qualcomm Incorporated |
| R3-243822 | Stage 2 update on AI/ML for NG-RAN | CATT, Nokia, ZTE, Ericsson, Huawei, Samsung |
| R3-243824 | Correction on textual description of Early Status Transfer procedure | ZTE Corporation, CMCC, China Unicom, CATT, Samsung, Nokia, Ericsson, China Telecom |
| R3-243825 | Correction on TAG information transfer for LTM | Samsung, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CATT, Google, LG Electronics, Lenovo, ZTE |
| R3-243826 | Correction on indirect Data forwarding[Indirect Data forwarding] | ZTE, LG Electronics, China Telecommunication, Huawei, Samsung |
| R3-243827 | Correction to QMC support in NR-DC for session status | Samsung, Ericsson, Xiaomi, China Unicom, Qualcomm Incorporated, Huawei, Nokia, ZTE |
| R3-243830 | Correction on BC session path update for network sharing | Huawei, CBN, Nokia, Qualcomm Incorporated, Samsung, CATT, ZTE, Ericsson |
| R3-243831 | Correction on MBS Broadcast F1-U Path Failure | Huawei, CBN, Nokia, Qualcomm Incorporated, Ericsson, CATT, ZTE |
| R3-243832 | Correction on indirect data forwarding [Indirect Data forwarding] | Huawei, Nokia, Samsung, LG Electronics, ZTE, Ericsson |
| R3-243833 | Corrections on CG-CandidateList to support S-CPAC | ZTE Corporation, Ericsson, CATT, China Telecom, CMCC, Samsung, Nokia, Lenovo, NEC, Google |
| R3-243840 | Corrections for CFRA resource provision in LTM | Google, Inc |
| R3-243841 | Corrections for LTM CSI Report Config generation | Google, Inc, ZTE, Huawei, Nokia, Samsung, CATT, LG Electronics, Lenovo, China Telecom, Ericsson |
| R3-243842 | Correcting IE referenced in Coverage Modification | Huawei, Nokia |
| R3-243843 | Correcting IE referenced in Coverage Modification | Huawei, Nokia |
| R3-243845 | Correction on Handover Cancel in CHO with SN for EN-DC | Samsung, ZTE, Ericsson, Huawei |
| R3-243854 | Correction on NGAP to support the QoE mobility during NG-based inter-MN HO | ZTE, China Unicom, China Telecom, CMCC, Samsung, CATT |
| R3-243855 | Correction on UL-RSCP | Ericsson, Nokia, Qualcomm Inc., Huawei, CATT |
| R3-243856 | Correction on UL-RSCP | Ericsson, Nokia, Qualcomm Inc., Huawei, CATT |
| R3-243867 | Correction on general F1AP principles for multicast reception in RRC_INACTIVE | ZTE, Ericsson, CMCC, Huawei |
| R3-243869 | Correction for 38.413 Reference specification | NEC, CMCC, NTT DOCOMO |
| R3-243870 | Correction on PSCell List Container List of RA report - XNAP | ZTE, CATT, China Telecom |
| R3-243871 | Correction on PSCell List of RA report | ZTE, CATT, China Telecom, CMCC, Samsung, Huawei, Ericsson, Nokia,China Unicom |
| R3-243874 | Correct the description of the selected PLMN indication in INITIAL UE MESSAGE | China Telecom, Huawei, CATT, ZTE, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-243875 | Correct the description of the selected PLMN indication in INITIAL UE MESSAGE | China Telecom, Huawei, CATT, ZTE, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-243876 | Addition of a missing indication in SN-initiated S-CPAC | Nokia |
| R3-243877 | Correction to DL-PRS Aggregation | Qualcomm Incorporated, Huawei, CATT |
| R3-243878 | Correction to DL-PRS Aggregation | Qualcomm Incorporated, Huawei, CATT |
| R3-243879 | [DRAFT] LS on Indicating Emergency Service Support over NG | RAN3(China Telecom) |
| R3-243883 | Correction on stage 2 LTM | CATT, China Telecom, ZTE, CMCC, Google, Inc., Nokia, LG Electronics, Lenovo, Ericsson, Huawei, Samsung |
| R3-243884 | Correction on the Assigned Criticality of LTM Cells To Be Released List IE | CATT, ZTE, Huawei, CMCC, Nokia, Samsung, LG Electronics, China Telecom, Lenovo, Ericsson |
| R3-243893 | Corrections for CFRA resource provision in LTM alternative 2 | Google, Inc |
| R3-243902 | Correction of Recovery of split PDU Session | Nokia, Huawei, Deutsche Telekom, ZTE, CATT, Ericsson |
| R3-243903 | (draft) LS on terminology definitions for AI-ML in NG-RAN | Ericsson, Huawei, Nokia, Telecom Italia, InterDigital, Deutsche Telekom, Lenovo, NEC |
| R3-243904 | Correction of Recovery of Split PDU Session | ZTE, Nokia, Huawei, Deutsche Telekom, Ericsson, CATT |
| R3-243905 | Correction of Recovery of Split PDU Session | Huawei, Nokia, Deutsche Telekom, ZTE, Ericsson, CATT |
| R3-243906 | Reply LS on Restoration procedures for a PDU Session with Dual Connectivity | RAN3(Ericsson) |
| R3-243907 | Correction on general F1AP principles for multicast reception in RRC_INACTIVE | ZTE, Ericsson, CMCC, Huawei, Nokia |
| R3-243909 | Correction of MBS F1-U failure Recovery - option 1 | Nokia, Huawei, Qualcomm Incorporated, Ericsson, ZTE |
| R3-243910 | Correction of MBS NG-U Setup and non shared gNB-DU | Nokia, Huawei, CATT, Qualcomm Incorporated, ZTE |
| R3-243911 | Correction on textual description of Early Status Transfer procedure for CHO | ZTE Corporation, CMCC, China Unicom, CATT, Samsung, Nokia, Ericsson, China Telecom, LG Electronics, Huawei |
| R3-243912 | Corrections for CFRA resource provision in LTM | Google, Inc, Nokia, ZTE, Samsung, CATT, LG Electronics, Lenovo |
| R3-243913 | Addition of a missing indication in SN-initiated S-CPAC | Nokia, LG Electronics, ZTE, Huawei, CATT, Samsung |
| R3-243914 | Correction for CHO cancel in UE CONTEXT MODIFICATION REQUEST | Huawei, Nokia, Ericsson, LG Electronics |
| R3-243915 | Correction on textual description of Early Status Transfer procedure for CPAC | ZTE Corporation, CMCC, China Unicom, CATT, Samsung, Nokia, Ericsson, China Telecom, LG Electronics, Huawei |
| R3-243916 | Correction on Inter-system MRO | Samsung, ZTE, Nokia, CMCC |
| R3-243917 | Correction on Inter-system MRO | Samsung, Nokia, ZTE, CMCC |
| R3-243920 | Correction to DL-PRS Aggregation | Qualcomm Incorporated, Huawei, CATT, Ericsson, ZTE |
| R3-243921 | Correction to DL-PRS Aggregation | Qualcomm Incorporated, Huawei, CATT, Ericsson, ZTE |
| R3-243922 | IAB-node authorization | CATT, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-243923 | Summary of Offline Discussion on CB: # 32_IAB | ZTE |
| R3-243927 | Correction on definition of AI/ML terminology | Samsung, ZTE, China Telecom, China Unicom, Telecom Italia, Huawei, Nokia, Deutsche Telekom, CMCC, CATT, Ericsson, NEC |
| R3-243928 | Stage 2 corrections for AI/ML for NG-RAN | Huawei, Nokia, Ericsson, InterDigital, NEC, Deutsche Telekom, Telecom Italia, CATT, Lenovo, ZTE, Samsung |
| R3-243930 | (draft) LS on terminology definitions for AI-ML in NG-RAN | Ericsson, Huawei, Nokia, Telecom Italia, InterDigital, Deutsche Telekom, Lenovo, NEC |
| R3-243931 | Correct the description of the selected PLMN indication in INITIAL UE MESSAGE | China Telecom, Huawei, CATT, ZTE, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-243932 | Correction on NGAP to support the QoE mobility during NG-based inter-MN HO | ZTE, China Unicom, China Telecom, CMCC, Samsung, CATT, Ericsson, Huawei |
| R3-243933 | LS on Indicating Emergency Service Support over NG | RAN3(China Telecom) |
| R3-243934 | IAB-node authorization | CATT, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-243940 | Support of PDCP SN Gap Report | Xiaomi, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Ericsson, Lenovo, CATT |
| R3-243942 | Correction on PSCell List Container List of RA report | ZTE, CATT, China Telecom, Nokia, Huawei, Ericsson, CMCC, China Unicom, Samsung |
| R3-243943 | Correction on of PSCell List of RA report | ZTE, CATT, China Telecom, Nokia, Huawei, Ericsson, CMCC, China Unicom, Samsung |
| R3-243945 | (draft) LS on terminology definitions for AI-ML in NG-RAN | RAN3(Ericsson) |
| R3-243948 | LS on terminology definitions for AI-ML in NG-RAN | RAN3(Ericsson) |
| R3-243965 | Correction of Recovery of split PDU Session | Nokia, Huawei, Deutsche Telekom, ZTE, CATT, Ericsson |
| R3-243966 | Correction on definition of AI/ML terminology | Samsung, ZTE, China Telecom, China Unicom, Telecom Italia, Huawei, Nokia, Deutsche Telekom, CMCC, CATT, Ericsson, NEC |
| R3-243967 | Correction on PSCell List Container List of RA report | ZTE, CATT, China Telecom, Nokia, Huawei, Ericsson, CMCC, China Unicom, Samsung |
| R3-243968 | Reply LS on Restoration procedures for a PDU Session with Dual Connectivity | RAN3(Ericsson) |
| R3-243969 | LS on terminology definitions for AI-ML in NG-RAN | RAN3(Ericsson) |
| R3-243975 | Correction on UL-RSCP | Ericsson, Nokia, Qualcomm Inc., Huawei, CATT |
| R3-243976 | Correction on UL-RSCP | Ericsson, Nokia, Qualcomm Inc., Huawei, CATT |
| 9.3 | R18 Rapporteur Corrections | |
| R3-243168 | Rapporteur Corrections | Huawei |
| R3-243169 | Rapporteur Corrections | Huawei |
| R3-243189 | NGAP rapporteur corrections | Nokia |
| R3-243190 | Rapporteur's editorial corrections for E1AP | Ericsson |
| R3-243257 | Rapporteur update for 36.401-CR | NEC |
| R3-243258 | Rapporteur update for 38.401-CR | NEC |
| R3-243349 | Rapporteur correction on IEs of INITIAL CONTEXT SETUP REQUEST message | Nokia, Nokia Shanghai Bell |
| R3-243350 | Rapporteur corrections on Conditional IEs | Nokia, Nokia Shanghai Bell |
| R3-243472 | NRPPa Rapporteur corrections | Ericsson |
| R3-243544 | Correcting ASN.1 comments for conditional present IE | Ericsson |
| R3-243545 | Correcting ASN.1 comments for conditional present IE | Ericsson |
| R3-243546 | Correcting ASN.1 comments for conditional present IE | Ericsson |
| R3-243547 | Correcting ASN.1 comments for conditional present IEs | Ericsson |
| R3-243548 | Correcting ASN.1 comments for conditional present IE | Ericsson |
| R3-243713 | Rapporteur corrections to R18 37.482 | Huawei |
| R3-243714 | Rapporteur corrections to R16 38.462 | Huawei |
| R3-243811 | Rapporteur corrections | Huawei |
| R3-243812 | Rapporteur corrections | Huawei |
| R3-243834 | Rapporteur's editorial corrections for E1AP | Ericsson |
| R3-243894 | Rapporteur update for 36.401 | NEC |
| R3-243895 | Rapporteur update for 38.401 | NEC |
| R3-243901 | Rapporteur Corrections | Huawei |
| R3-243908 | NRPPa Rapporteur corrections | Ericsson |
| 9.4 | Endorsed TEI CRs Review | |
| R3-243031 | Introduction of XR Broadcast Information IE for XnAP [2Rx_XR_Device] | ZTE, Qualcomm, China Telecom, Xiaomi, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Huawei, CATT |
| R3-243032 | Correction for RAN TSS reporting for multiple TSCTSF | Nokia, Ericsson, Huawei, Qualcomm Incorporated, ZTE |
| R3-243033 | Correction on XnAP PPID and Destination Port Number over SCTP | NTTDOCOMO, INC. |
| R3-243034 | Correction on the MT communication handling procedure | Huawei, ZTE, Ericsson, Nokia, CATT, Qualcomm Incorporated, China Telecom |
| R3-243035 | Correction of Time Reference Information | Huawei, Nokia, ZTE, Ericsson, Deutsche Telekom |
| R3-243036 | Correction of Time Reference Information | Huawei, Nokia, ZTE, Ericsson, Deutsche Telekom |
| R3-243037 | Correction of Time Reference Information | Huawei, Nokia, ZTE, Ericsson, Deutsche Telekom |
| R3-243038 | Introduction of 2Rx XR support [2Rx_XR_Device] | Nokia, Nokia Shanghai Bell, ZTE, Qualcomm, China Telecom, Xiaomi, Samsung, Ericsson, CMCC, Huawei, CATT |
| R3-243039 | Correction on missing procedure for positioning | ZTE, CATT, Ericsson, Huawei, Xiaomi, Nokia |
| R3-243040 | Rapporteur corrections to 37.482 | Huawei |
| R3-243041 | RedCap UE MBS Broadcast reception [RedcapMBS] | Huawei, CBN, Qualcomm Incorporated, ZTE, Nokia, Ericsson, Lenovo |
| R3-243042 | Correction on SDT RRC Release with resume indication [SDT_ReleaseEnh] | ZTE, Huawei, China Telecom, Qualcomm, LG Electronics, China Unicom, Samsung, CATT |
| R3-243043 | SDT RRC Release with resume indication [SDT_ReleaseEnh] | Huawei, Qualcomm Incorporated, Lenovo, ZTE, LG Electronics, Samsung |
| R3-243044 | Introduction of 2Rx XR support [2Rx_XR_Device] | Samsung, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, ZTE, CMCC, Huawei, Qualcomm, CATT, Xiaomi |
| R3-243045 | IAB-node de-registration handling | CATT, Ericsson, Huawei, ZTE |
| R3-243046 | IAB-node De-registration Handling | Ericsson, Huawei, CATT, ZTE |
| R3-243047 | Correction on IAB-node de-registration handling | Huawei, Ericsson, CATT, ZTE |
| R3-243048 | Correction on IAB-node de-registration handling | Huawei, Ericsson, CATT, ZTE |
| R3-243049 | IAB-node De-registration Handling | ZTE, Ericsson, Huawei, CATT |
| R3-243050 | Support of no PDU session for IAB-MT during Path Switch Request procedure | ZTE, Qualcomm, Nokia, Nokia Shanghai Bell, Huawei, Lenovo, Samsung |
| R3-243051 | Support of no PDU session for IAB-MT during Path Switch Request procedure | ZTE, Qualcomm, Nokia, Nokia Shanghai Bell, Huawei, Lenovo, Samsung |
| R3-243052 | Correction on mobility support for mobile IAB without PDU session | Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, Lenovo, Samsung |
| R3-243053 | Corrections on mobile IAB procedures | CATT, Huawei, Fujitsu, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Ericsson |
| R3-243054 | Correction on mobile IAB-MT migration | Huawei, CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-243055 | Correction on the LTM configuration ID and LTM configuration ID Mapping list | CATT, China Telecom, Nokia, Nokia Shanghai Bell, Samsung, Google, CMCC, ZTE, Huawei, Ericsson, NEC, LG Electronics |
| R3-243056 | Introduction of MDBV in the Alternative QoS | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm, ZTE, China Telecom, Ericsson, CMCC, Xiaomi, Samsung, Lenovo, CATT |
| R3-243057 | Introduction of MDBV in the Alternative QoS | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm, ZTE, China Telecom, Ericsson, CMCC, Xiaomi, Samsung, Lenovo, CATT |
| R3-243058 | Correction on MDBV for alternative QoS | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, China Telecom, Ericsson, Samsung, Xiaomi, CMCC, Lenovo, CATT |
| R3-243059 | Correction on MDBV for alternative QoS | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, China Telecom, Ericsson, Samsung, Xiaomi, CMCC, Lenovo, CATT |
| R3-243060 | Clarification on non-homogeneous deployment | Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT, Ericsson, Qualcomm Inc, CMCC, Xiaomi, Samsung, Lenovo, CATT |
| R3-243061 | Correction on DL PSI based discard | Huawei, CATT, CMCC, Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, China Telecom |
| R3-243062 | Correction of MT Communication Handling procedure | Ericsson, Huawei, Nokia, Xiaomi, Qualcomm Inc., ZTE, CATT |
| R3-243063 | UL SDT for MT communication handling | ZTE, Qualcomm, CATT, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Xiaomi |
| R3-243064 | Correction on MT Communication Handling Procedures in TS 38.410 | China Telecom, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-243065 | Correction on missing IE for sidelink DRX reference-option1 | ZTE Corporation, Sanechips, China Telecom, Samsung, Nokia, Nokia Shanghai Bell, LG Electronics Inc., Ericsson |
| R3-243066 | Introduction of SL related information transmission over F1 interface | NEC, ZTE, Samsung, CMCC |
| R3-243067 | Introduction of SL related information transmission over F1 interface | NEC, ZTE, Samsung, CMCC |
| R3-243068 | Correction on S1AP PPID and Destination Port Number over SCTP | NTTDOCOMO, INC. |
| R3-243069 | Correction on F1AP PPID and Destination Port Number over SCTP | InterDigital |
| R3-243070 | Correction on X2AP PPID and Destination Port Number over SCTP | NTTDOCOMO, INC. |
| R3-243071 | Correction on NGAP PPID and Destination Port Number over SCTP | NTTDOCOMO, INC. |
| R3-243072 | Correction on measurement report for SRS Bandwidth Aggregation | ZTE, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi |
| R3-243073 | Correction on user consent for trace reporting | CMCC, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-243074 | Correction on text description of UE trajectory information | ZTE, CATT, Samsung, China Unicom, Lenovo, NEC, Ericsson, Nokia |
| R3-243075 | Correction of handling GTP-U Error Indication | Nokia, Ericsson, Huawei, ZTE |
| R3-243076 | Correction of handling GTP-U Error Indication | Huawei, Nokia, Ericsson, ZTE |
| R3-243077 | Introduction of Measurement Quality and Time Stamp Information to E-CID [ECIDQualTimeStamp] | Ericsson, Comtech, Verizon Wireless, Polaris Wireless, Nokia, ZTE |
| R3-243078 | Introduction of Measurement Quality and Time Stamp Information to E-CID [ECIDQualTimeStamp] | Ericsson, Comtech, Verizon Wireless, Polaris Wireless, Nokia, ZTE |
| R3-243079 | Introduction of Measurement Quality and Time Stamp Information to E-CID [ECIDQualTimeStamp] | Ericsson, Comtech, Verizon Wireless, Polaris Wireless, Nokia, ZTE |
| R3-243080 | Correction on musim-CapabilityRestrictionIndication IE | Ericsson, Qualcomm Incorporated, Xiaomi |
| R3-243081 | Correction on burst arrival time in handover | Lenovo, Huawei, CATT, CMCC, ZTE, Xiaomi, Samsung, Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-243082 | Clarification of the bearer menagement in case of CHO with SCG | Nokia, LG Electronics |
| R3-243083 | Stage2 correction on direct data forwarding | Samsung, CATT, Huawei, Cybercore, ZTE, Nokia, LG Electronics, Ericsson |
| R3-243084 | Correction for early sync and TCI state of LTM | NEC, Google Inc., LG Electronics, ZTE, Huawei, Samsung, CATT, China Telecom, CMCC, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, Rakuten |
| R3-243085 | Corrections on LTM procedures | China Telecom, Huawei, CATT, Nokia, Nokia Shanghai Bell, Google, ZTE, Ericsson, LG Electronics, NEC, CMCC |
| R3-243086 | LTM corrections to F1AP | Huawei, China Telecom, CATT, Google, Inc., Ericsson, Nokia, LG Electronics, ZTE, Lenovo |
| R3-243087 | Further corrections on LTM in stage-2 | Ericsson, Nokia, Lenovo, ZTE, Google Inc., LG Electronics Inc., CATT |
| R3-243088 | Further corrections on LTM over F1 | Ericsson, CATT, Huawei, Nokia, LG Electronics, Lenovo, ZTE |
| R3-243089 | Corrections for LTM for reconfiguration with sync | Google, Inc, CATT, Nokia, Ericsson, LG Electronics, Huawei, China Telecom, NEC, Lenovo, ZTE, CMCC |
| R3-243090 | Rel-18 LTM correction for LTM with gNB-CU-UP change | LG Electronics, Google, Ericsson, Nokia, Huawei, CATT, Lenovo, ZTE, CMCC, NEC, China Telecom, Samsung |
| R3-243091 | Corrections for DU-CU/CU-DU Cell Switch notification message | ZTE, Nokia, Ericsson, Huawei, CATT, China Telecom, LG Electronics, Lenovo |
| R3-243092 | Correction on non-integer DRX cycle | Huawei, Lenovo, China Telecom, Nokia, Nokia Shanghai Bell, ZTE, CATT, Ericsson, Qualcomm, LG Electronics Inc., Samsung, CMCC |
| R3-243093 | Addition of missing positioning SIBs | Nokia, CATT, Ericsson, Huawei, Qualcomm Incorporated, Samsung, Xiaomi, ZTE |
| R3-243094 | Corrections for SL Relay N3C related description | NEC, LG Electronics, Nokia, Nokia Shanghai Bell, Samsung, Ericsson |
| R3-243095 | Corrections on SL relay | LG Electronics, Nokia, Nokia Shanghai Bell, Samsung, Ericsson |
| R3-243096 | Corrections on PC5 RLC channel configuration for U2U relay | ZTE, Samsung, China Telecom, NEC, Sanechips, LG Electronics, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-243097 | Correction on measurement report for SRS Bandwidth Aggregation | CATT, ZTE, Ericsson, Huawei, Nokia, Samsung, Xiaomi |
| R3-243098 | Various corrections on Rel-18 Positioning | Huawei, CATT, Ericsson, Nokia, Xiaomi, Samsung, ZTE |
| R3-243099 | Various corrections on Rel-18 Positioning | Huawei, CATT, Ericsson, Nokia, Xiaomi, Samsung, ZTE |
| R3-243100 | Addition of missing positioning SIBs | Huawei, Nokia, CATT, Ericsson, Qualcomm Incorporated, Samsung, Xiaomi, ZTE |
| R3-243101 | Addition of missing positioning SIBs | Huawei, Nokia, CATT, Ericsson, Qualcomm Incorporated, Samsung, Xiaomi, ZTE |
| R3-243102 | Stage 3 corrections for AI/ML for NG-RAN | Huawei, Nokia, Qualcomm Incorporated, InterDigital, NEC, ZTE, CMCC, Ericsson, CATT |
| R3-243160 | Correction on MT Communication Handling Procedures in TS 38.410 | China Telecom, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-243452 | Correction on F1AP PPID and Destination Port Number over SCTP | InterDigital |
| R3-243774 | Corrections for LTM for reconfiguration with sync | Google, Inc, CATT, Nokia, Ericsson, LG Electronics, Huawei, China Telecom, NEC, Lenovo, ZTE, CMCC |
| R3-243789 | LTM corrections to F1AP | Huawei, China Telecom, CATT, Google, Inc., Ericsson, Nokia, LG Electronics, ZTE, Lenovo |
| R3-243799 | Correction on user consent for trace reporting | CMCC, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-243800 | LTM corrections to F1AP | Huawei, China Telecom, CATT, Google, Inc., Ericsson, Nokia, LG Electronics, ZTE, Lenovo |
| R3-243944 | LTM corrections to F1AP | Huawei, China Telecom, CATT, Google, Inc., Ericsson, Nokia, LG Electronics, ZTE, Lenovo |
| 10.1 | General | |
| R3-243661 | Workplan for Rel-19 SON_MDT Enhancement | China Unicom, CMCC |
| 10.2 | MRO Enhancements | |
| R3-243144 | Further discussion on the optimal usage of Subsequent CPAC | Nokia |
| R3-243164 | Discussion on LTM MRO enhancement | Fujitsu |
| R3-243165 | MRO enhancement for R18 mobility mechanisms | Huawei |
| R3-243194 | MRO enhancements for R18 mobility mechanisms | Qualcomm Incorporated |
| R3-243248 | MRO for LTM | NEC |
| R3-243249 | MRO for Subsequent CPAC | NEC |
| R3-243260 | MRO enhancements for LTM and CHO with candidate SCGs | Ericsson |
| R3-243267 | Discussion on MRO for LTM | Samsung |
| R3-243279 | Discussion on MRO for CHO with candidate SCGs and S-CPAC | Samsung |
| R3-243379 | Discussion on MRO for LTM | Lenovo |
| R3-243380 | Discussion on MRO for subsequent CPAC and CHO with candidate SCGs | Lenovo |
| R3-243419 | MRO Enhancements for LTM and CHO with Candidate SCG(s) | Nokia |
| R3-243636 | (TP for TS 38.300) Discussion on MRO for LTM | CATT |
| R3-243637 | (TP for TS 37.340) Discussion on MRO for CHO with candidate SCG and SCPAC | CATT |
| R3-243647 | Discussion on MRO enhancements for LTM | China Telecom |
| R3-243662 | Discussion on MRO Enhancements | China Unicom |
| R3-243690 | Discussion on scenarios of failure LTM and near-failure LTM | LG Electronics Inc. |
| R3-243691 | Discussion on CHO with candidate SCG(s) failure cases | LG Electronics Inc. |
| R3-243708 | Discussion on MRO | ZTE |
| R3-243733 | Discussion on MRO enhancements for R18 mobility features | CMCC |
| R3-243846 | SoD of MRO for LTM | Ericsson |
| R3-243847 | SoD of MRO for others | Huawei |
| 10.3.1 | Intra-NTN Mobility | |
| R3-243145 | Further discussion on MRO enhancements for NTN deployments | Nokia |
| R3-243195 | SON MDT for NTN | Qualcomm Incorporated |
| R3-243205 | SON for Intra-NTN mobility | Huawei |
| R3-243261 | SON/MDT enhancements for NTN | Ericsson |
| R3-243278 | Discussion on SON enhancements for NTN | Samsung |
| R3-243381 | Discussion on MRO for intra-NTN mobility | Lenovo |
| R3-243571 | Discussion on SONMDT enhancements for NTN | ZTE |
| R3-243627 | Discussion on SON enhancements for NTN | China Telecommunication |
| R3-243638 | Discussion on intra-NTN mobility for SONMDT | CATT |
| R3-243663 | Discussion on SONMDT enhancements for NTN mobility | China Unicom |
| R3-243717 | Discussion on SON/MDT enhancement for NTN | CMCC |
| R3-243848 | SoD of SONMDT NTN related | CATT |
| 10.3.2 | Network Slicing | |
| R3-243146 | Further discussion on SON enhancements for network slicing | Nokia |
| R3-243166 | SON for Network Slicing | Huawei |
| R3-243196 | SON MDT for network slicing | Qualcomm Incorporated |
| R3-243262 | Discussion on Slice-aware MRO use cases | Ericsson |
| R3-243263 | MDT enhancements for Network Slicing | Ericsson, InterDigital, Deutsche Telekom |
| R3-243264 | (TP for SON BL CR for TS 38.413) MDT enhancements for Network Slicing | Ericsson, InterDigital, Deutsche Telekom |
| R3-243265 | Draft LS on MDT enhancements for Network Slicing | Ericsson, InterDigital, Deutsche Telekom |
| R3-243639 | Discussion on network slicing for SONMDT | CATT |
| R3-243664 | Discussion on SONMDT enhancements for network slicing | China Unicom |
| R3-243709 | Further consideration on SON/MDT for Slicing | ZTE |
| R3-243725 | Discussion on SONMDT for network slicing | CMCC |
| R3-243849 | SoD of SONMDT slicing related | China Unicom |
| 10.4 | R18 leftovers | |
| R3-243167 | Rel-18 SON/MDT leftovers | Huawei |
| R3-243266 | Further discussion on RACH optimization for SDT | Ericsson |
| R3-243285 | Discussion on the support of the leftovers in Rel-18 SON/MDT | Samsung |
| R3-243382 | Discussion on RACH optimization for SDT | Lenovo |
| R3-243572 | Discussion on Rel-18 leftover issues | ZTE |
| R3-243665 | Discussion on RACH optimization for SDT | China Unicom |
| R3-243734 | Discussion on SON/MDT Enhancements for SDT | CMCC |
| R3-243850 | SoD of SONMDT leftovers | CMCC |
| 11.1 | General | |
| R3-243170 | Skeleton for TR38.743 v0.0.1 | ZTE |
| R3-243756 | Updated Work plan for Study on enhancements for Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN | ZTE, NEC |
| R3-243971 | Skeleton for TR38.743 | ZTE |
| 11.2 | AI/ML enabled Slicing | |
| R3-243256 | (TP to TR38.743) AI/ML-based Network Slicing | NEC |
| R3-243268 | (TP to TR 38.743) AI/ML enabled slicing | Samsung |
| R3-243289 | (TP for TR 38.743 )Support of AI/ML enabled slicing | CATT |
| R3-243383 | Discussion on AIML based network slicing | Lenovo |
| R3-243384 | TP to 38.743 for AIML based network slicing | Lenovo |
| R3-243410 | TP on AIML for Network Slicing | Ericsson, InterDigital, Deutsche Telekom, Telecom Italia |
| R3-243416 | AIML for Network Slicing | Ericsson, InterDigital, Deutsche Telekom, Telecom Italia |
| R3-243466 | (TP to TR 38.743) Discussion on the AI/ML- enabled Network Slicing | Huawei |
| R3-243490 | (TP for TR 38.743) Further discussion on AI/ML Network Slicing | Nokia, Telecom Italia |
| R3-243498 | (TP to TR38.743) AI/ML assisted Network Slicing | ZTE |
| R3-243558 | Discussion on NG-RAN AI/ML for Network Slicing | Qualcomm Incorporated |
| R3-243718 | Discussion on AI-based network slice | CMCC |
| R3-243801 | CB:#AIML1_Slicing | CATT |
| R3-243918 | (TP for TR 38.743 )Support of AI/ML enabled slicing | CATT, Huawei, Nokia, ZTE, Samsung, NEC, CMCC, Ericsson, Lenovo |
| 11.3 | AI/ML enabled Coverage and Capacity Optimization | |
| R3-243124 | (TP for TR 38.743) Further discussion on solution for AI/ML-based CCO | Nokia |
| R3-243255 | (TP to TR38.743) AI/ML based CCO | NEC |
| R3-243269 | (TP to TR 38.743) AI/ML enabled CCO | Samsung |
| R3-243290 | (TP for TR 38.743 )Support of AI/ML enabled CCO | CATT |
| R3-243346 | Identification and rectification of coverage holes using AI-ML | Rakuten Mobile, Inc |
| R3-243385 | Discussion on AI/ML based CCO | Lenovo |
| R3-243386 | TP to 38.743 for AIML based CCO | Lenovo |
| R3-243450 | TP on AIML support for CCO | Ericsson, InterDigital, Deutsche Telekom, Telecom Italia |
| R3-243458 | Further discussion on AIML support for CCO | Ericsson, InterDigital, Deutsche Telekom, Telecom Italia |
| R3-243467 | (TP to TR 38.743) AI/ML-based Coverage and Capacity Optimization | Huawei |
| R3-243499 | Discussion on AI/ML assisted CCO | ZTE |
| R3-243500 | (TP to TR38.743) Discussion on AI/ML assisted CCO | ZTE |
| R3-243559 | Discussion on AI/ML enabled CCO | Qualcomm Incorporated |
| R3-243603 | Discussion on AI/ML based Coverage and Capacity Optimization | China Telecommunication |
| R3-243604 | (TP to 38.743) Support of AI/ML based Coverage and Capacity Optimization | China Telecommunication |
| R3-243692 | Issues on AI/ML-based CCO | LG Electronics Inc. |
| R3-243693 | (TP to TR 38.743) Issues on AI/ML-based CCO | LG Electronics Inc. |
| R3-243719 | Discussion on AI/ML-based CCO | CMCC |
| R3-243767 | Identification and Rectification of CCO Issues Using AIML | Rakuten Mobile, Inc |
| R3-243802 | CB:#AIML2_CCO | Qualcomm |
| R3-243939 | (TP for TR 38.743) AI/ML enabled CCO | Qualcomm |
| 11.4 | R18 leftovers | |
| R3-243115 | Multi hop UE trajectory Feedback | InterDigital |
| R3-243253 | Discussion on AI/ML Rel-18 leftovers | NEC |
| R3-243254 | (TP to TR38.743) Split architecture support for Rel-18 use cases | NEC |
| R3-243270 | (TP to TR 38.743) AI/ML for mobility in NR-DC | Samsung |
| R3-243271 | (TP to TR 38.743) AI/ML for NG-RAN in split architecture | Samsung |
| R3-243272 | (TP to TR 38.743) Continuous MDT collection targeting the same UE across RRC states | Samsung |
| R3-243273 | (TP to TR 38.743) Multi-hop UE trajectory across gNBs | Samsung |
| R3-243291 | (TP for TR 38.743 )Support of AL/ML for NG-RAN in NR-DC scenario and Split architecture | CATT |
| R3-243292 | (TP for TR 38.743 )Support of multi-hop UE trajectory prediction/feedback | CATT |
| R3-243387 | Discussion on other leftover issues | Lenovo |
| R3-243388 | TP to 38.743 for other leftover issues | Lenovo |
| R3-243417 | TP on multi-hops UE Trajectory | Ericsson |
| R3-243418 | Discussion on solutions for multi-hops UE Trajectory | Ericsson |
| R3-243425 | Discussion on anonymization requirement for M-based MDT | CATT |
| R3-243426 | [Draft] LS for anonymization requirement for M-based MDT | CATT |
| R3-243447 | (TP for TR 38.743) TP on Continuous MDT and UE measurement correlation | Ericsson, Deutsche Telekom, InterDigital |
| R3-243448 | TP on AI/ML Network Energy Saving | Ericsson, AT&T, T-Mobile US, NTT DoCoMo, Deutsche Telekom, BT, Vodafone, Telecom Italia, Verizon |
| R3-243449 | AI/ML Network Energy Saving | Ericsson, AT&T, T-Mobile US, NTT DoCoMo, Deutsche Telekom, BT, Vodafone, Telecom Italia, Verizon |
| R3-243451 | Continuous MDT and UE measurement correlation | Ericsson, Deutsche Telekom, InterDigital |
| R3-243453 | Discussion on AI/ML for split architecture use cases | Ericsson |
| R3-243459 | Further discussion on Mobility Optimization for NR-DC | Ericsson, Deutsche Telekom, InterDigital, AT&T |
| R3-243460 | Improved granularity for Energy Cost | Ericsson |
| R3-243461 | TP on Mobility Optimization for NR-DC | Ericsson, Deutshce Telekom, InterDigital, AT&T |
| R3-243462 | TP on Improved Granularity for Energy Cost | Ericsson |
| R3-243463 | TP on Split architecture support for Rel-18 use cases | Ericsson |
| R3-243468 | On the prioritization for Rel-18 AI/ML for NG-RAN leftovers | Huawei |
| R3-243469 | Rel-18 leftovers: AI/ML-based mobility enhancements | Huawei |
| R3-243470 | Split architecture support for Rel-18 “AI/ML for NG-RAN” use cases | Huawei |
| R3-243471 | On Continuous MDT for AI/ML | Huawei |
| R3-243491 | (TP for TR 38.743) Mobility Optimization for NR-DC | Nokia |
| R3-243492 | (TP for TR 38.743) Split Architecture Support for the Rel-18 AI/ML Use Cases | Nokia |
| R3-243493 | AI/ML Energy Saving Enhancements | Nokia, Deutsche Telekom, T-Mobile USA, Vodafone, Verizon, Telecom Italia, BT |
| R3-243494 | (TP for TR 38.743) AI/ML Energy Saving Enhancements | Nokia, Deutsche Telekom, T-Mobile USA, Vodafone, Verizon, Telecom Italia, BT |
| R3-243495 | (TP for TR 38.743) Continuous Management-based MDT Data Collection | Nokia |
| R3-243496 | (TP for TR 38.743) AI/ML Multi-hop UE Trajectory | Nokia |
| R3-243497 | AI/ML Model Inference in the gNB-DU | Nokia, Deutsche Telekom, Huawei, BT, T-Mobile USA, Verizon |
| R3-243501 | (TP to TR38.743) Mobility Optimization for NR-DC and split architecture support | ZTE |
| R3-243502 | (TP to TR38.743) Continuous MDT collection | ZTE |
| R3-243503 | (TP to TR38.743) Multiple hop UE trajectory and energy saving enhancements | ZTE |
| R3-243560 | Discussion on Continuous MDT | Qualcomm Incorporated |
| R3-243561 | Discussion on Multihop UE Trajectory Prediction and Feedback | Qualcomm Incorporated |
| R3-243645 | Discussion on AI/ML based Mobility Optimization for NR-DC | China Telecom |
| R3-243646 | (TP to TR38.743) Support of AI/ML based Mobility Optimization for NR-DC | China Telecom |
| R3-243694 | Discussion on mobility optimization for NR-DC | LG Electronics Inc. |
| R3-243715 | Discussion on AI/ML based Mobility Optimization for NR-DC | CMCC |
| R3-243716 | Discussion on Multi-hop UE trajectory across gNBs | CMCC |
| R3-243721 | Discussion on AI/ML for split architecture use cases | CMCC |
| R3-243722 | Further Discussion on AI/ML Network Energy Saving | CMCC |
| R3-243803 | CB:#AIML3_Leftover | ZTE |
| R3-243925 | [TP for TR38.743] Rel-18 Leftovers | ZTE |
| R3-243926 | (TP for TR 38.743) Continuous Management-based MDT Data Collection | Nokia |
| R3-243951 | [TP for TR38.743] Rel-18 Leftovers | ZTE, Huawei, CATT, Nokia, Lenovo, NEC, Samsung, CMCC, Ericsson, InterDigital |
| R3-243952 | (TP for TR 38.743) Continuous Management-based MDT Data Collection | Nokia, Huawei, Qualcomm, NEC, Samsung, ZTE, CMCC, InterDigital, Ericsson |
| 12.1 | General | |
| R3-243171 | TR skeleton for additional topological enhancements for NR | NTT DOCOMO INC., AT&T |
| R3-243970 | TR skeleton for additional topological enhancements for NR | NTT DOCOMO INC., AT&T |
| 12.2 | Wireless Access Backhaul (WAB) | |
| R3-243021 | LS on FS_VMR_Ph2 solution impacts to RAN | SA2(Qualcomm) |
| R3-243174 | Discussion on Wireless Access Backhaul | NTTDOCOMO, INC. |
| R3-243199 | (draft Reply LS) Discussion on reply LS to SA2 on VS_VMR_Ph2 solution impacts on RAN | Qualcomm Inc. |
| R3-243200 | (TP to TR 38.799) WAB requirements and archtiecture | Qualcomm Inc. |
| R3-243201 | (TP to TR 38.799) WAB network integration and mobility | Qualcomm Inc. |
| R3-243202 | (TP to TR 38.799) WAB resource coordination | Qualcomm Inc. |
| R3-243217 | (TP to TR 38.799) Discussion on architecture and protocol stack for R19 WAB | ZTE |
| R3-243218 | (TP to TR 38.799) Discussion on supporting WAB and the reply LS on FS_VMR_Ph2 solution impacts to RAN | ZTE |
| R3-243219 | (TP to TR 38.799) Discussion on WAB mobility and resource multiplexing | ZTE |
| R3-243247 | Consideration on architecture and mobility for WAB | NEC |
| R3-243305 | (TP for TR 38.799) General aspects of WAB | Xiaomi |
| R3-243306 | (TP for TR 38.799) SA2’s LS for WAB | Xiaomi |
| R3-243327 | (TP to TR 38.799) Discussion on impact of WAB | CATT |
| R3-243328 | (draft reply LS) Discussion on LS for VMR from SA2 | CATT |
| R3-243329 | (TP to TR 38.799) Discusson on resource multiplexing for WAB | CATT |
| R3-243339 | Discussion on the Architecture, Access control and QoS support of WAB | Huawei |
| R3-243340 | Discussion on the procedures related to the WAB | Huawei |
| R3-243341 | Discussion on SA2's LS (S2-2405822/R3-243021) on FS_VMR_Ph2 solution impacts to RAN | Huawei |
| R3-243351 | (TP to draft TR 38.799) Discussion on WAB architecture and high level aspects | Nokia, Nokia Shanghai Bell |
| R3-243352 | Discussion on WAB integration and mobility | Nokia, Nokia Shanghai Bell |
| R3-243353 | Resource Multiplexing for WAB | Nokia, Nokia Shanghai Bell |
| R3-243361 | (pCR for TR 38.799) WAB Architecture and Scenarios | Ericsson |
| R3-243362 | (pCR for TR 38.799) Functional Aspects of WAB-Nodes | Ericsson |
| R3-243363 | Handling of Backhaul Link Degradation and Resource Multiplexing for WAB | Ericsson |
| R3-243389 | Discussion on integration procedure for WAB node | Lenovo |
| R3-243390 | Discussion on migration procedure for WAB node | Lenovo |
| R3-243391 | Discussion on resource multiplexing for WAB node | Lenovo |
| R3-243581 | Discussion on enhancements for WAB | CANON Research Centre France |
| R3-243583 | Discussion on RAN impact of SA2 solution in WAB | LG Electronics |
| R3-243584 | (TP for TR 38.799) Architecture and protocol stack for WAB’s Xn | LG Electronics |
| R3-243585 | Reply LS on FS_VMR_Ph2 solution impacts to RAN | LG Electronics |
| R3-243588 | Views on FS_VMR_Ph2 Solution Impacts to RAN | China Telecom |
| R3-243648 | (TP to TR 38.799) Discussion on network integration for WAB | Samsung |
| R3-243649 | (TP to TR 38.799) Discussion on WAB mobility | Samsung |
| R3-243809 | Summary of Offline Discussion on additional topological enhancement | NTTDOCOMO, INC. |
| R3-243844 | CB:#WAB | NTT DOCOMO |
| R3-243859 | (TP for TR 38.799) on architecture | Nokia |
| R3-243860 | (TP to TR 38.799) On WAB authorization | CATT, Xiaomi, Lenovo, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, Qualcomm, Huawei, ZTE |
| R3-243861 | (pCR for TR 38.799): Mobility Support for WAB-Nodes | Ericsson |
| R3-243862 | (TP for TR 38.799) on other issues | ZTE, China Telecom, Huawei, Nokia, Nokia Shanghai Bell, Ericsson, CATT |
| R3-243863 | (TP for TR 38.799) on integration procedure | Huawei, Nokia, Nokia Shanghai Bell, CATT, Samsung, Ericsson, Xiaomi, ZTE, Lenovo |
| R3-243864 | Reply LS on FS_VMR_Ph2 solution impacts to RAN | RAN3(Qualcomm) |
| R3-243959 | (TP for TR 38.799) on architecture | Nokia, Nokia Shanghai Bell, ZTE, Xiaomi, CATT, Huawei, China Telecom, Qualcomm, Samsung, Lenovo, Ericsson |
| R3-243960 | (pCR for TR 38.799): Mobility Support for WAB-Nodes | Ericsson |
| R3-243961 | Reply LS on FS_VMR_Ph2 solution impacts to RAN | RAN3(Qualcomm) |
| 12.3 | 5G Femto | |
| R3-243020 | LS on Support of UE move between CAG cell of 5G Femto and CSG cell | SA2(Docomo) |
| R3-243025 | LS to request clarification on the potential baseline system architecture of 5G NR Femto | SA3(China mobile) |
| R3-243175 | Discussion on NR Femto | NTTDOCOMO, INC. |
| R3-243176 | draft Reply LS on Support of UE move between CAG cell of 5G Femto and CSG cell | NTTDOCOMO, INC. |
| R3-243187 | 5G femto architecture considerations | AT&T Services, Inc. |
| R3-243197 | Comment on Femto architecture options 1 and 2 | Charter Communications, Inc |
| R3-243198 | Xn Gateway in Femto architecture | Charter Communications, Inc |
| R3-243203 | (draft Reply LS) Discussion on reply LS to SA2 on Support of UE move between CAG cell of 5G Femto and CSG cell | Qualcomm Inc. |
| R3-243232 | Access to local services from the 5G Femto via distributed UPF | Huawei |
| R3-243252 | Open issues on NR femto | NEC |
| R3-243315 | Discussion on NG connection and interface for Option 2 for NR Femto Architecture | Baicells |
| R3-243316 | (TP to TR 38.799)NG connection and interface for Option 2 for NR Femto Architecture | Baicells |
| R3-243330 | (TP to TR 38.799) On 5G Femto architecture | CATT |
| R3-243331 | (TP to TR 38.799) On 5G Femto local service access | CATT |
| R3-243332 | (TP to TR 38.799) On 5G Femto access control mechanism | CATT |
| R3-243342 | Discussion on the architecture and access control for NR Femto | Huawei |
| R3-243343 | Discussion on SA2’s LS (S2-2405813/ R3-243020) on Support of UE move between CAG cell of 5G Femto and CSG cel | Huawei |
| R3-243374 | NR Femto Architecture and Ongoing Issues | Ericsson LM |
| R3-243392 | Architecture for NR Femto | Lenovo |
| R3-243393 | Access control and handover for NR Femto with CAG | Lenovo |
| R3-243394 | Discussion on interworking between CAG and CSG cells | Lenovo |
| R3-243409 | NR Femto Node Access Control with CAG | Ericsson LM |
| R3-243411 | Access to Local Services via Local UPF | Ericsson LM |
| R3-243562 | [TP for TR 38.799] Evaluation of NR Femto Architecture Options | Nokia, TMO US, AT&T, Verizon Wireless, KDDI, British Telecom, NTT Docomo Charter |
| R3-243563 | Support of UE Move between CAG cell and CSG cell | Nokia |
| R3-243564 | Reply LS on Support of UE move between CAG cell of 5G Femto and CSG Cell | Nokia |
| R3-243565 | [TP for TR 38.799] Access to Local Services | Nokia |
| R3-243586 | Discussion on SA2 solutions to support HO between CAG and CSG cell | LG Electronics |
| R3-243587 | Reply LS on Support of UE move between CAG cell of 5G Femto and CSG cell | LG Electronics |
| R3-243607 | On Access Control for NR Femto | China Telecom |
| R3-243608 | On Architecture for NR Femto Support | China Telecom |
| R3-243650 | (TP to TR 38.799) Discussion on Femto architecture | Samsung |
| R3-243651 | (TP to TR 38.799) Discussion on access control for NR Femto | Samsung |
| R3-243686 | draft Reply LS to request clarification on the potential baseline system architecture of 5G NR Femto | NTTDOCOMO, INC. |
| R3-243753 | (TP to TR 38.799)Discussion on architecture and access control of NR Femto | ZTE |
| R3-243754 | (TP to TR 38.799)Discussion on support of local services | ZTE |
| R3-243755 | Discussion on CSG-CAG mobility | ZTE |
| R3-243761 | Draft Reply LS to request clarification on the potential baseline system architecture of 5G NR Femto | CMCC |
| R3-243828 | Adding SeGW to NR Femto Architecture Options 1, 3 and 4 | Ericsson |
| R3-243835 | (TP to TR38.799) for option B of Xn support | Huawei |
| R3-243837 | (TP for TR 38.799) OptionA without Xn gateway | ZTE |
| R3-243851 | Adding SeGW to NR Femto Architecture Options 1, 3 and 4 | Ericsson, Huawei, Nokia, Lenovo, ZTE, Samsung |
| R3-243852 | (TP for TR 38.799) OptionA without Xn gateway | ZTE, Huawei, Nokia, Lenovo |
| R3-243853 | [TP for TR 38.799] Evaluation of NR Femto Architecture Options | Nokia |
| R3-243857 | [DRAFT] Reply LS on Support of UE move between CAG cell of 5G Femto and CSG cell | Ericsson |
| R3-243947 | [DRAFT] Reply LS on Support of UE move between CAG cell of 5G Femto and CSG cell - alternative | Ericsson |
| R3-243953 | [TP for TR 38.799] Evaluation of NR Femto Architecture Options | Nokia, Huawei |
| 13.2 | Support for inter-CU LTM | |
| R3-243106 | Discussion on Inter-gNB-CU LTM Procedure | Nokia |
| R3-243107 | Additional Considerations for Inter-gNB-CU LTM | Nokia |
| R3-243108 | TP (BL CR TS 38.401) Inter-CU LTM Signalling | Nokia |
| R3-243114 | LS on security handling for inter-CU LTM in non-DC cases | RAN2(Apple) |
| R3-243163 | Discussion on CFRA resource configurations in inter-CU LTM | Google Inc. |
| R3-243206 | Discussion on Inter-CU LTM | Huawei |
| R3-243207 | (TP for LTM BLCR for TS38.300): Inter-CU LTM basic procedure | Huawei |
| R3-243208 | (TP for LTM BLCR for TS 38.473): F1 impact for Inter-CU LTM | Huawei |
| R3-243241 | Regarding discussion on inter-CU LTM | NEC |
| R3-243293 | Radio Resource management at gNB-DU for Intra and Inter-CU LTM | Rakuten Mobile, Inc |
| R3-243294 | Data forwarding and transmission in Inter-CU LTM | Rakuten Mobile, Inc |
| R3-243369 | TP (BL CR TS 38.401) Inter-CU LTM Signalling | Nokia |
| R3-243395 | General aspects of inter-CU LTM | Lenovo |
| R3-243396 | [TP for TS 38.423] Inter-CU LTM | Lenovo |
| R3-243397 | Security considerations of inter-CU LTM | Lenovo |
| R3-243420 | Discussion for Inter-CU LTM | CATT |
| R3-243421 | Discussion about candidate cell management and signalling designation | CATT |
| R3-243422 | TP for LTM BLCR for TS38.300 | CATT |
| R3-243455 | High level design principle for inter-CU LTM | Ericsson |
| R3-243456 | Details of XnAP signaling design | Ericsson |
| R3-243457 | Consideration of data forwarding for inter-CU LTM | Ericsson |
| R3-243522 | Inter-gNB LTM and keep PDCP anchor | Qualcomm Incorporated, NTT DOCOMO |
| R3-243523 | Support for inter-CU LTM | Qualcomm Incorporated |
| R3-243528 | Further discussions on Inter-CU LTM signaling design | LG Electronics Inc. |
| R3-243529 | Baseline CR for introducing Rel-19 Mobility enhancement in E1AP | LG Electronics Inc. |
| R3-243595 | Discussion on inter-CU LTM | ZTE |
| R3-243596 | (TP to TS 38.423) Support of inter-CU LTM | ZTE |
| R3-243597 | (BL CR to 38.420) Introduction of inter-CU LTM | ZTE |
| R3-243642 | Discussion on signaling enhancement for inter-CU LTM | China Telecom |
| R3-243643 | (TP to BL CR of 38.420) On support of inter-CU LTM | China Telecom |
| R3-243644 | (TP to BL CR of 38.423) On support of inter-CU LTM | China Telecom |
| R3-243668 | Discussion on Inter-CU LTM | Samsung |
| R3-243669 | (TP to BLCR for TS 38.423) Xn impact for Inter-CU LTM | Samsung |
| R3-243670 | (TP to BLCR for TS 38.401/38.300) Procedure for Inter-CU/gNB LTM | Samsung |
| R3-243735 | Discussion on inter-CU LTM | CMCC |
| R3-243772 | Response to R3-243114 | LG Electronics Inc. |
| R3-243836 | CB:#25_LTMprocedure | China Telecom |
| 14.1 | General | |
| R3-243671 | Updated work plan for NR_NTN_Ph3 | CATT, Thales |
| 14.2 | Support MBS broadcast service | |
| R3-243220 | Discussion on Support of MBS Broadcasting over NTN access | TCL |
| R3-243242 | Discussion on NR NTN supporting MBS broadcast service | NEC |
| R3-243298 | (TP to TS 38.413) Support of Intended area | Xiaomi |
| R3-243354 | (TP for TS 38.300) Discussion on the support of MBS Broadcast Service | Nokia, Nokia Shanghai Bell |
| R3-243398 | Support of broadcast service in NTN | Lenovo |
| R3-243412 | MBS Service Area in NR NTN | Ericsson, Eutelsat Group, SES, Thales |
| R3-243433 | (TP for TS 38.413 and TS 38.300) Support MBS broadcast service | Huawei |
| R3-243464 | Broadcast Service Area for NR NTN | Ericsson |
| R3-243553 | Discussion on MBS broadcast additional features for NR NTN Evolution | THALES |
| R3-243557 | (TP for TS38.300) Discussion on Support for NR NTN MBS Broadcast Service | Qualcomm Incorporated |
| R3-243617 | Further discussion on support MBS broadcast service for NR NTN | Samsung |
| R3-243628 | Discussion on support MBS broadcast service for NTN | China Telecommunication |
| R3-243654 | Discussion on NTN broadcast service supporting with TP to TS 38.300 | ZTE |
| R3-243672 | (TP for BL CRs) Support of MBS broadcast service for NR NTN | CATT |
| R3-243723 | Discussion on Supporting MBS broadcast service for NR NTN | CMCC |
| 14.3 | Support of Regenerative payload | |
| R3-243017 | LS on Support of Regenerative-based Satellite Access | SA2(VIVO) |
| R3-243023 | Reply LS on security of IP transport over satellite transport links (S3-240950 / S2-240390) | SA2(Ericsson) |
| R3-243221 | Discussion on Regenerative NTN Architecture | TCL |
| R3-243243 | Discussion on NR NTN supporting the regenerative payload | NEC |
| R3-243299 | (TPs to TS 38.300 and 38.413) support of regenerative payload | Xiaomi |
| R3-243355 | (TP for TS 38.300 and TS 38.413) Discussion on the support of Regenerative payload | Nokia, Nokia Shanghai Bell |
| R3-243399 | Mobility issues for regenerative payload in NTN | Lenovo |
| R3-243413 | Support for Regenerative Payload in NR NTN | Ericsson, Thales, Deutsche Telekom, Nokia, ESA, CATT, ZTE, Sateliot, Huawei |
| R3-243414 | NTN Regenerative Payload in Rel-19 | Ericsson, Sateliot |
| R3-243415 | [DRAFT] Reply LS on security of IP transport over satellite transport links | Ericsson LM |
| R3-243432 | Support of regenerative payload (including LS responses) | Huawei |
| R3-243530 | Satellite on-board gNB identification in 5G system | LG Electronics Inc. |
| R3-243531 | CR for Satellite on-board gNB identification in 5G system | LG Electronics Inc. |
| R3-243556 | Discussion on NG Signaling impacts for NR NTN Regenerative Payload | Qualcomm Incorporated |
| R3-243567 | Support of regenerative payload (including LS responses) | Huawei |
| R3-243573 | Discussion on support of regenerative payload | ZTE |
| R3-243618 | Further discussion on support of regenerative payload for NR NTN | Samsung |
| R3-243629 | On support of regenerative payload in NR NTN | China Telecommunication |
| R3-243673 | Discussion on support of regenerative payload | CATT |
| R3-243724 | Discussion on Support of regenerative payload for NR NTN | CMCC |
| R3-243858 | Reply LS on security of IP transport over satellite transport links | RAN3(Ericsson) |
| R3-243865 | Discussion on support of regenerative payload | ZTE |
| R3-243866 | Support for Regenerative Payload in NR NTN | Ericsson, Thales, Deutsche Telekom, Nokia, ESA, CATT, ZTE, Sateliot, Huawei |
| R3-243949 | Support for Regenerative Payload in NR NTN | Ericsson, Thales, Deutsche Telekom, Nokia, ESA, CATT, ZTE, Sateliot, Huawei, Dish Networks, Echostar, Eutelsat Group, Xiaomi, Samsung, CMCC, LG Electronics |
| R3-243954 | Reply LS on Support of Regenerative-based Satellite Access | RAN3(ZTE) |
| R3-243955 | Reply LS on security of IP transport over satellite transport links | RAN3(Ericsson) |
| 16.1 | General | |
| R3-243103 | TR 38.769 skeleton for Study on solutions for Ambient IoT in NR | Huawei, CMCC |
| R3-243736 | Work Plan for Ambient IoT SI | CMCC, Huawei, T-Mobile USA |
| R3-243972 | (BL pCR to TR 38.769) Study on solutions for Ambient IoT in NR | Huawei, CMCC |
| 16.2 | RAN Architecture | |
| R3-243128 | [TP for TR 38.769] RAN Architecture and Protocol Stack for AIoT | Nokia |
| R3-243133 | (TP for TR38.769) RAN architecture for Ambient-IoT | ZTE |
| R3-243134 | [Draft] LS on CN-RAN interface design for Ambient-IoT | ZTE |
| R3-243191 | Architecture aspects and Protocol stack for Ambient IoT | Qualcomm Incorporated |
| R3-243233 | Consideration on RAN architecture aspects | Huawei |
| R3-243244 | RAN architecture discussion on ambient IoT | NEC |
| R3-243295 | AIoT RAN architecture | Xiaomi |
| R3-243400 | [TP for TR 38.769] RAN architecture considerations of Ambient IoT | Lenovo |
| R3-243549 | On functional split between RAN and CN | Ericsson |
| R3-243551 | [DRAFT] LS on AIoT - RAN3 assumptions on functional split between RAN and CN | Ericsson |
| R3-243619 | Further discussion on RAN architecture for Ambient IoT | Samsung |
| R3-243630 | Discussion on AIoT RAN architecture | China Telecommunication |
| R3-243674 | (TP for TR 38.769) Consideration on A-IoT architecture aspects | CATT |
| R3-243737 | Discussion on RAN Architecture for Ambient IoT | CMCC |
| R3-243807 | [TP for TR 38.769] CB:#AIoT1_Architecture | Ericsson, Huawei |
| R3-243962 | [TP for TR 38.769] CB:#AIoT1_Architecture | Ericsson, Huawei |
| 16.3 | RAN-CN Interface Impact | |
| R3-243129 | Paging Signalling Impacts for AIoT | Nokia |
| R3-243130 | [TP for TR 38.769] Paging Signalling Impacts for AIoT | Nokia |
| R3-243131 | [TP for TR 38.769] Data Transport and Context Management for AIoT | Nokia |
| R3-243135 | (TP for TR38.769) NG interface impact for Ambient-IoT | ZTE |
| R3-243192 | Paging, device context management and data transport for Ambient IoT | Qualcomm Incorporated |
| R3-243234 | Inventory over CN-RAN interface | Huawei |
| R3-243235 | Command and Context management over CN-RAN interface | Huawei |
| R3-243245 | RAN-CN interface impact on ambient IoT | NEC |
| R3-243296 | AIoT interface impacts between RAN and CN | Xiaomi |
| R3-243401 | [TP for TR 38.769] Paging considerations of Ambient IoT | Lenovo |
| R3-243402 | [TP for TR 38.769] Device context management considerations of Ambient IoT | Lenovo |
| R3-243403 | [TP for TR 38.769] Data transport considerations of Ambient IoT | Lenovo |
| R3-243550 | Nature and Content of Information exchanged between RAN and CN for Ambient IoT | Ericsson |
| R3-243609 | Discussion on Paging and Context Management for Ambient IoT | China Telecom |
| R3-243620 | Further discussion on RAN-CN interface impact for Ambient IoT | Samsung |
| R3-243675 | (TP for TR 38.769) On A-IoT Inventory and Command services | CATT |
| R3-243676 | (TP for TR 38.769) A-IoT device context management and Data transport | CATT |
| R3-243738 | Discussion on paging for Ambient IoT | CMCC |
| R3-243739 | Discussion on Device Context Management and Data Transfer | CMCC |
| R3-243769 | Discussion on NG impact for Ambient IoT | LG Electronics |
| R3-243808 | Summary of Offline Discussion – CB: # AIoT2_CNRANinterface | Huawei |
| R3-243872 | Inventory and Command between AIoT CN amd AIoT RAS | Huawei, CMCC, Nokia, Ericsson, ZTE, Xiaomi, Qualcomm Incorporated, Samsung, CATT, Lenovo, LG Electronics, NEC |
| R3-243963 | Inventory and Command between AIoT CN amd AIoT RAS | Huawei, CMCC, Nokia, Ericsson, ZTE, Xiaomi, Qualcomm Incorporated, Samsung, CATT, Lenovo, LG Electronics, NEC Electronics, NEC |
| 16.4 | Others | |
| R3-243136 | (TP for TR38.769) Locating Ambient-IoT device | ZTE |
| R3-243193 | Methods for locating an Ambient IoT device | Qualcomm Incorporated |
| R3-243236 | Location report of Ambient IoT devices | Huawei |
| R3-243246 | Further discussion on ambient IoT locating | NEC |
| R3-243297 | Locating AIoT device | Xiaomi |
| R3-243552 | On locating AIoT devices | Ericsson |
| R3-243677 | Consideration on locating of A-IoT device | CATT |
| R3-243740 | Discussion on locating Ambient IoT device | CMCC |
| R3-243810 | CB:#AIoT3_Location | CMCC |
| R3-243950 | (TP for TR38.769) Locating Ambient-IoT device | CMCC, ZTE, CATT, Xiaomi, LGE, Huawei, Lenovo, NEC |
| R3-243964 | (TP for TR38.769) Locating Ambient-IoT device | CMCC, ZTE, CATT, Xiaomi, LGE, Huawei, Lenovo, NEC |
| 17.1 | General | |
| R3-243535 | WI Work plan for R19 Network Energy Savings | Ericsson |
| 17.2 | Support on-demand SSB SCell operation | |
| R3-243125 | On-Demand SSB SCell operation for UEs in connected mode | Nokia |
| R3-243177 | Discussion on on-demand SSB SCell operation | Huawei |
| R3-243274 | Discussion on on-demand SSB SCell operation | Samsung |
| R3-243334 | Discussion on support on-demand SSB SCell operation | CATT |
| R3-243404 | Discussion on On-demand SSB for SCell | Lenovo |
| R3-243536 | On-demand SSB SCell operation | Ericsson |
| R3-243574 | Discussion on on-demand SSB Scell operation | ZTE |
| R3-243727 | Discussion on On-Demand SSB SCell Operation Support | CMCC |
| 17.3 | Support on-demand SIB1 for UEs | |
| R3-243126 | Discussion on RAN3 impacts for On-Demand SIB1 Support | Nokia |
| R3-243178 | (TP for TS 38.473) Discussion on on-demand SIB1 for UEs | Huawei |
| R3-243204 | Aspects of on-demand SIB1 for NES enhancements | Qualcomm Inc. |
| R3-243250 | On-demand SIB1 transmission of a NES cell | NEC |
| R3-243251 | [draft] LS on one case of on-demand SIB1 transmission | NEC |
| R3-243275 | Discussion on on-demand SIB1 | Samsung |
| R3-243333 | Discussion on on-demand SIB1 for idle UE | CATT |
| R3-243405 | Discussion on On-demand SIB1 for Idle/Inactive UE | Lenovo |
| R3-243537 | On-demand SIB1 transmission | Ericsson |
| R3-243575 | Discussion on on-demand SIB1 for idle/inactive mode UEs | ZTE |
| R3-243726 | (TP for TS 38.473) Support On-Demand SIB1 for Ues | CMCC |
| R3-243868 | CB:#19 Summary of offline discussions: Support on-demand SIB1 for Ues | Ericsson |
| 21.1 | General | |
| R3-243018 | LS on Application-Layer FEC Awareness at RAN | SA2(Qualcomm) |
| R3-243019 | LS on FS_XRM Ph2 | SA2(VIVO) |
| R3-243104 | (BL CR to 37.340) Support of XR enhancements | ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Inc, Lenovo, Huawei, Ericsson, CATT, CMCC, Samsung, Xiaomi |
| R3-243105 | Support of XR enhancements | CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei, CMCC |
| R3-243172 | Draft Reply LS on FS_XRM Ph2 | Qualcomm Incorporated |
| R3-243300 | Discussion on SA2 LS for R19 XR | Xiaomi |
| R3-243344 | Discussion on SA2's LS (R3-243016/S2-2405625) on FS_XRM Ph2 | Huawei |
| R3-243356 | Work Plan for Rel-19 on XR Enhancements for NR | Nokia, Nokia Shanghai Bell |
| R3-243357 | Discussion on the SA2 LS | Nokia, Nokia Shanghai Bell |
| R3-243406 | Discussion on replies to SA2 LS on FS_XRM Ph2 | Lenovo |
| R3-243484 | Discussion on LS from SA2 | Ericsson |
| R3-243641 | Reply to LS on FS_XRM Ph2 | CATT |
| R3-243688 | Work Plan for Rel-19 on XR Enhancements for NR | Nokia, Qualcomm (Rapporteurs) |
| R3-243745 | Discussion on LS from SA2 on LS on FS_XRM Ph2 | vivo |
| R3-243919 | Response LS on FS_XRM Ph2 | RAN3(Lenovo) |
| R3-243958 | Response LS on FS_XRM Ph2 | RAN3(Lenovo) |
| R3-243973 | (BL CR to 37.340) Support of XR enhancements | ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Inc, Lenovo, Huawei, Ericsson, CATT, CMCC, Samsung, Xiaomi |
| R3-243974 | Support of XR enhancements | CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei, CMCC |
| 21.2 | Support XR in DC | |
| R3-243173 | R19 XR DC Signaling Enhancements | Qualcomm Incorporated |
| R3-243239 | (TP to TS 38.423 on Support of XR in DC) ECN Marking/Congestion Information Reporting on SN Terminated bearer | NEC |
| R3-243240 | (TP to TS 38.423 on Support of XR in DC) PSI-Based SDU Discarding | NEC |
| R3-243345 | (TP for NR_XR_Ph3 BL CR) Enhancement for NR-DC support of XR | Huawei |
| R3-243358 | (TP to BL CR for TS 38.423) Discussion on the support of XR in NR-NR DC | Nokia, Nokia Shanghai Bell |
| R3-243407 | (TP to BLCR for 37.340) Burst Arrival Time handling in NR-DC | Lenovo, Samsung, ZTE, Qualcomm Incorporated, Xiaomi, Huawei, CATT |
| R3-243408 | Remaining issues on PSI discard, ECN marking and End of Data Burst | Lenovo |
| R3-243483 | (TP to BLCR for 38.423) Remaining issues for support of XR in DC | Ericsson |
| R3-243485 | Support for L4S in DC | Ericsson, Deutsche Telekom, Charter, BT |
| R3-243486 | Support for L4S in NR-NR DC | Ericsson, Deutsche Telekom, Charter, BT |
| R3-243487 | (TP to TS38.423) Support for L4S in DC | Ericsson, Deutsche Telekom, Charter, BT |
| R3-243598 | Discussion on support XR in DC | ZTE |
| R3-243599 | (TP to TS 37.340 and 38.423) Support XR in DC | ZTE |
| R3-243640 | Discussion on XR in DC | CATT |
| R3-243652 | Discussion on support XR in DC | Samsung |
| R3-243653 | (TP to TS 38.423) Support XR in DC | Samsung |
| R3-243728 | (TP to TS 38.423 and 37.340) Support of XR in DC | CMCC |
| R3-243729 | Discussion on support XR in DC | CMCC |
| R3-243820 | CB:#XR2_NRDC | Nokia |
| R3-243896 | (TP to BL CR for TS 38.423) Support ECN Marking and Congestion Information Reporting in DC | Ericsson |
| R3-243897 | (TP to BL CR for TS 37.340) Burst Arrival Time handling in NR-DC | Huawei, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Xiaomi, Samsung |
| R3-243898 | (TP to BL CR for TS 38.423) PSI-Based SDU Discarding | NEC, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, Xiaomi, Samsung |
| R3-243899 | (TP to BL CR for TS 37.340) End of Data Burst Indication handling in NR-DC | Lenovo, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-243900 | (draft) LS on UL PSI based PDU discarding in NR-DC | RAN3(Qualcomm) |
| R3-243946 | (TP to BL CR for TS 38.423) Support ECN Marking and Congestion Information Reporting in DC | Ericsson |
| R3-243956 | (TP to BL CR for TS 38.423) Support ECN Marking and Congestion Information Reporting in DC | Ericsson, Deutsche Telekom, Charter, BT, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung |
| R3-243957 | LS on UL PSI based PDU discarding in NR-DC | RAN3(Qualcomm) |